Play / The map / The capabilities / Run programs as the account
Run programs as the account
execute.process.host — execute × process at host reach (the machine, container or account it runs as). Family: process. Effect: recoverable from a backup, a history or a revert, at a cost.
Granted by 6 of 9
| Profile | Control on the path | Evidence | Via |
|---|---|---|---|
| Claude Code — web container | ● none | observed | shell (Bash) |
| Claude Code — local · confirm off | ● none | derived | shell (Bash) |
| Claude Code — local · confirm on | ◐ setting | derived | shell (Bash) |
| Claude Desktop — local tools | ◐ setting | derived | local files and commands (when enabled) |
| Scheduled job — service account | ● none | derived | the job |
| GitHub Actions — hosted runner | ● none | observed | the job's shell |
What narrows it
The setting: keep the confirmation prompt on for commands, and run in a container: execution survives inside it and stops being execution on your machine
What it costs: a click per command · an afternoon for the container
Tier after: setting (prompt) · boundary (container)
Questions that ask about it
- Have you ever clicked something that said 'always allow', or turned its confirmations off? — eliciting, reliability 0.6
In the mandates
- wanted by A coding assistant on my machine
- wanted by A coding assistant in a container on the web
- wanted by A CI job on a hosted runner
- wanted by A scheduled job under a service account
- not wanted by The desktop app, with local tools switched on
- not wanted by Chat in the browser, nothing connected