agy Script Kit DevTools
This skill is the fast-agent companion to $script-kit-devtools. It does not
replace the direct DevTools contract; it wraps it with an agy prompt so a
faster model can infer the likely surface, run the existing scripts/devtools/*
CLI primitives, and return a compact inspection report.
Use this when the user wants agy to inspect Script Kit GPUI from a prompt, or
when a quick first-pass app investigation is useful before deeper Codex or
Oracle work.
Front Door
Run the wrapper from the repo root:
scripts/agentic/agy-devtools.sh run --prompt "The actions dialog shortcuts overlap on notes" --surface actions-dialog
Important options:
--prompt <text>: required user report or inspection request.--prompt-file <path>: read the user request from a file.--surface <id>: optional hint such asmain,actions-dialog,notes,dictation,agent_chat,file-search, orsettings.--session <name>: DevTools session name hint passed toagy; defaults toagy-devtools.--trust-repo: pass--dangerously-skip-permissionstoagy; use only after reviewing the prompt and safety gates.--agy-sandbox on|off: keep sandbox on by default; turn it off only whenagyneeds to run local DevTools commands.--fast: use a short command-budget prompt for known action flows, especially demos where source exploration would be noise.--allow-act,--allow-submit,--allow-native,--allow-mic,--allow-real-data: explicit opt-ins for actions, submit/Enter flows, native input, live microphone, or real-data mutation.
The wrapper writes each run under .test-output/agy-devtools/<run-id>/:
input.txt: the raw user request.inference.json: deterministic surface, target, safety, and primitive-stack inference.prompt.md: the exact prompt sent toagy.agy.log: the CLI log from--log-file.agy.stdout.mdandagy.stderr.log: rawagy --printoutput streams.result.json,result.md, andcompact.md: final result files.receipts/: expected location for any DevTools JSON receipts thatagycreates.
Subcommands
run: build prompt, invokeagy, save logs/results, and print compact output.infer: infer surface, target, safety gates, and primitive stack as JSON.prompt: write and print the exactagyprompt without invokingagy.compact: print compact summary for an existing--run-dir.cleanup: stop a named wrapper-owned DevTools session.
agy Contract
agy must stay inside the existing DevTools layer:
- Infer the likely surface and target from the user prompt and any
--surfacehint. - Start with source-backed orientation commands such as
bun scripts/devtools/investigate.ts,inspect.ts,targets.ts,elements.ts,layout.ts,focus.ts,text.ts,scroll.ts,keyboard.ts,events.ts, orcoverage.ts. - Use
scripts/agentic/devtools-session.shwhen a real app session is needed. - Write JSON receipts to the provided
receipts/directory. - Produce a final Markdown report with classification, commands run, receipt paths, key findings, likely owner files, and next verification.
Safety Rules
- Default mode is inspect-only. Do not submit forms, press Enter on selected rows, invoke destructive built-ins, or use native input unless the wrapper prompt includes the matching allow flag.
- If a required primitive is missing, classify the run as
blocked-by-missing-primitiveand name the exact missing primitive. - Do not call a screenshot-only observation green for a behavior bug. Green means the same failed user-path measurement now passes.
- Treat user interruption, hidden windows, missing target identity, and stale sessions as explicit classifications, not generic failures.
Verification
For wrapper changes, run:
scripts/agentic/agy-devtools.sh --help
scripts/agentic/agy-devtools.sh infer --prompt "Cmd-K opens the actions popup but it is clipped" --surface auto
scripts/agentic/agy-devtools.sh run --dry-run --prompt "inspect the main menu filter" --surface main
scripts/agentic/agy-devtools.sh run --dry-run --fast --prompt "Open Agent Chat and submit what's for lunch" --surface agent_chat --allow-act --allow-submit
scripts/agentic/agy-devtools.sh run --dry-run --fast --prompt "Open the theme designer, change the accent color to red" --surface theme --allow-act --allow-submit --allow-real-data
If behavior changes beyond prompt assembly, add the smallest source or runtime proof that can fail for the changed contract.