Repository navigation
0.2.14
·
300 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Improved
- The agent runs in the job's own checkout and home again, through a copy-on-write view, as 0.2.12 introduced and 0.2.13 reverted. What
setup:prepares — a toolchain, a warm cache, a generated file — is there for the agent at the pathsetup:left it, and nothing the agent writes reaches the runner's disk or a later step. The checkout no longer carries the sandbox's write-protection stubs that failedgit add -Aunder 0.2.12, and the agent starts in a repository without.claude/. Anythingsetup:leaves readable in the runner's home, exports to$GITHUB_ENV, or sets in job-levelenv:is readable by the agent, and so by a pull request's own code: log in only in steps tend does not run. A self-hosted runner whose work folder is outside the runner account's home fails in the "Set up credential-isolation sandbox" step, naming both paths. (#1346) sandbox_setup:,sandbox_path:, andsandbox_env:are deprecated, andinitmigrates them, since the agent now runs with the job's own PATH and environment.initwarns, and turns each key into onesetup:step after the consumer's own:sandbox_envvalues sit in that step'senv:, where an expression still evaluates, and are exported to$GITHUB_ENV;sandbox_pathentries become$GITHUB_PATHlines that keep their order; andsandbox_setup's commands share one bash step. A migrated command no longer has tend'suvon PATH, so one that callsuvneedsastral-sh/setup-uvearlier insetup:. The actions'sandbox_envinput is removed, and a later release will refuse all three keys. (#1346, #1355)- The agent's sandbox is a hardened systemd unit instead of Anthropic Sandbox Runtime. Jobs no longer install the sandbox runtime, bubblewrap, socat, or ripgrep, or toggle AppArmor's user-namespace restriction. The unit runs as the non-sudo sandbox user in a private network namespace whose only route is the proxy on loopback, with private
/tmp,/dev/shm, and/dev, other users' processes hidden, andAF_UNIXsockets still refused. It also refuses new namespaces, so a tool that builds its own sandbox from one (bubblewrap, a rootless container runtime, Chromium's sandbox) cannot start.ALL_PROXYandGRPC_PROXYare no longer set;rgis whatever the runner image or the harness provides, so a consumer whose instructions call it installs it insetup:; and masked runner files fail with "permission denied" rather than reading as empty. Thesandbox_runtime_versionaction input is removed. Requires kernel 5.19, util-linux 2.39, and systemd 247, whichubuntu-24.04has. (#1354) /tend-ci-runner:open-prreserves a closing keyword for a PR that settles the whole report. A PR that settles part of one writesRefs #Nand names what it leaves, in the body and the commit message alike, andtriageno longer ends every fix withCloses #N. (#1353)
Fixed
- The sandbox reap waits for the killed sandbox user's processes to exit, re-issuing the kill until
pgrepfinds none or 10 s pass. It sampled once right after the kill, so a process still tearing down failed the job withsandbox UID still owns a live process after reap. (#1352) list_recent_runs.pywarns when a run in the census was re-run, naming each one. A run's conclusion is its latest attempt's, so a failure cleared by a re-run left no row andreview-runsreported fewer failures than the window had. (#1337)- Generated workflows no longer fold long YAML values across lines. A long
if:orenv:expression stays on one line with no trailing space, and a workflow override no longer adds line breaks to mention's prompt. (#1355)
Documentation
docs/security-model.mdrecords the claude.ai account surface — skills, plugins, and MCP connectors synced from the bot's account — and the three session settings that refuse it. Its agent-execution-boundary section describes the systemd unit. (#1349, #1354)
Internal
test-sandboxasserts from inside the unit that DNS is unreachable, other users' processes are hidden,unshare --userfails, and/dev/shmis private, and afterwards that notend-*unit or view mount remains. (#1354)