Home / The model / The capabilities / execute.process.host
execute.process.host
Run programs as the account. Verb execute, object process, reach host, family process. Its effect is with-effort: undone at a cost.
In 6 of 9 published shapes
| Deployment shape | Barrier there | Known by | Note | |
|---|---|---|---|---|
| ● | Claude Code on the web (a remote session container) | none (not a control) | observed | root inside the container: every process and file IN THE CONTAINER. The container is the host; your machine is not reachable |
| ● | Claude Code (the CLI, on your own machine) | none (not a control) | derived | |
| ◐ | Claude Code (the CLI, on your own machine) | setting (not a control) | derived | |
| ◐ | Claude Desktop (a desktop app with local tools) | setting (not a control) | derived | run terminal commands as you |
| ● | A scheduled job running as a service account | none (not a control) | derived | as the service account, on a schedule |
| ● | Actions runner (a hosted CI job) | none (not a control) | observed | runs as uid 1001; passwordless escalation available (n1a) - programs run as this user and can escalate |
| Barrier | What stands in the way | Is it a control | |
|---|---|---|---|
| ● | none | nothing in the way | no |
| ◉ | expectation | a rule in prose, enforced by nobody | no |
| ◐ | setting | a switch the agent's own account can flip | no |
| ○ | boundary | enforced above the grant, out of the agent's reach | yes |
What the starting mandates say about it
| The mandate says | Which mandates |
|---|---|
| authorised | A coding assistant on my machine, A coding assistant in a container on the web, A CI job on a hosted runner, A scheduled job under a service account |
| refused | The desktop app, with local tools switched on, Chat in the browser, nothing connected |
| unstated | Chat, with connectors switched on, A browser extension I installed |
Unstated is not authorised. A mandate that never mentioned a capability did not authorise it, and the delta on every example page counts it as excess and says which kind it was.
What would move it to the fourth barrier
| What | What it costs | The barrier afterwards |
|---|---|---|
| keep the confirmation prompt on for commands, and run in a container: execution survives inside it and stops being execution on your machine | a click per command · an afternoon for the container | setting (prompt) · boundary (container) |
This is a published reduction, not a recommendation. Whether it is worth doing depends on the assets and the consequences, which are not in this document and are not this site's to guess.