Scenarios

A scenario starts an agent, sends scripted keys, and records the signals: screens, hook payloads, session files, and open files. A probe only reads sessions that already run (see probes/README.md). A scenario makes its own session.

Path: scenarios/<agent>/<name>.sh. Shared functions: scenarios/lib.sh.

Rules for a scenario

1. It runs the agent in a throwaway HOME and a private tmux server (tmux -L). The cleanup trap kills the server and deletes the throwaway folder.
2. It copies a login into the throwaway HOME only with copy_login. copy_login refuses a login that is near its expiry, because a token refresh in the copy could make the original login fail.
3. An API key goes to the agent through a file that only the owner can read, never through the command line.
4. Its prompts are neutral text that can be public. A prompt that must open a permission dialog asks for a file write in the throwaway folder.
5. Its output goes to out/, which git ignores. Do not commit it. Send it through the scrub before it goes into a CI log or an artifact.
6. The header of the script says what it needs, what it costs, and which questions it answers.

Scenarios

CI (.github/workflows/scenarios.yml) runs first-run.sh for each agent on 10 Linux and macOS labels, in four agent groups (a to d), and windows-installs.ps1 and first-run-windows.ps1 on windows-2022, windows-2025 and windows-11-arm, in four agent groups, by hand and once a week. It needs no secret. A start by hand can select one job with the input job.