You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 77e9afd
Browse filesBrowse the repository at this point in the historyBrowse files
feat(machine): make a running machine's own files immutable in run jails
During `agent6 machine run`, the machine's own `.asm.toml` and its `scripts/`
bundle (when under the jail-mounted cwd) are marked read-only in every jail the
run spawns — tool-state jails via a new `LiveWorld.protect_paths`, and agent
`run_command` jails via a new `ToolDispatcher(extra_protect_paths=...)` threaded
through the agent subprocess. Layered alongside the existing protect_git /
protect_agent6 read-only carve-outs.
So a tool or agent state (even one with run_command and network) cannot rewrite
its own machine logic, add an `allow_network` flag, or alter an audited bundle
script — mid-run or for a future run. The stored run copy under
`.agent6/machines/` was already covered by protect_agent6.
Security review note: defense-in-depth for the supervisor egress model — the
machine artifact the operator reviewed stays fixed for the duration of the run.
Files outside cwd aren't in the child's view, so only in-cwd machine files are
(and need to be) protected. No jail/Rust changes — reuses extra_protect_paths.
0 commit comments