Development record
An agent abcd starts without a terminal has nobody to answer the host's permission prompts. A command the host cannot check is then refused, and the lane stalls or fails. The product thinker chose to have abcd answer those prompts for the agents it starts, using its existing guard rules.
issueresolvedminoriss-2610161612203555
An agent abcd starts without a terminal has nobody to answer the host's permission prompts. A command the host cannot check is then refused, and the lane stalls or fails. The product thinker chose to have abcd answer those prompts for the agents it starts, using its existing guard rules.
Grounds
- pursued: a headless lane's shell commands stop stalling on prompts nobody answers, while hazards, protected-path writes and critical-path removals stay refused; a lane refused on a command the guard reads whole and clears, or a hazard that runs unasked, would show it wrong
Frontmatter
| id | iss-2610161612203555 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610161612203555-an-agent-abcd-starts-without-a-terminal.md
open on GitHub ↗ · commit history ↗
mentions4
- adr-2610161621415708Unattended runs abcd launches execute inside an OS sandbox
- dcn-26101616122696472026-10-16 — Agents keep running past the host's permission prompts in two ways (product thinker, 2026-10-16): abcd teaches agents the command forms the host can check (iss-2610161612200864), and, for the agents abcd itself starts without a terminal, abcd answers the prompts per launch with its guard rules (iss-2610161612203555). abcd does not approve commands in interactive sessions, does not sandbox, and never edits the person's host settings.
- itd-2610161621364075The agents abcd launches on its own work inside a sandbox the operating system enforces
- spc-2610161751056096a-person-who-leaves-abcd-to-run-on-its