Today archie picks up a forge issue, runs an agent in a sandboxed task container and commits through the daemon. #1978 and #2012 delete that path without a replacement, so the capability would disappear at slice 6.
Keep it as a document kind the engine executes: a task-triggered workflow whose agent runs in the runner's sandbox (profiles, egress allowlist, the network grant of #1968), whose brief goes in /.git/task.json, and whose commits and pushes are made by the daemon, never the model. The repo stays one optional input, so nothing else in the product assumes it.
Done when: an issue with a task label produces a run that ends in a commit or a pull request, shown in the dashboard like any other run.
Today archie picks up a forge issue, runs an agent in a sandboxed task container and commits through the daemon. #1978 and #2012 delete that path without a replacement, so the capability would disappear at slice 6.
Keep it as a document kind the engine executes: a task-triggered workflow whose agent runs in the runner's sandbox (profiles, egress allowlist, the network grant of #1968), whose brief goes in <worktree>/.git/task.json, and whose commits and pushes are made by the daemon, never the model. The repo stays one optional input, so nothing else in the product assumes it.
Done when: an issue with a task label produces a run that ends in a commit or a pull request, shown in the dashboard like any other run.
sam
added the featurehigh labels 2026-11-16 01:24:27 +00:00
Part of epic #1977. The dependency could not be recorded: this Gitea's dependency write endpoint answers 404 and the connector that used to add it is disconnected, so this comment carries the link.
Part of epic #1977. The dependency could not be recorded: this Gitea's dependency write endpoint answers 404 and the connector that used to add it is disconnected, so this comment carries the link.
Maintainer decision: the archie-agent worker moves into the runner's sandbox rather than being deleted. Sandboxed agents are part of what Archie sells (risk, governance, security). Only its NATS transport goes (internal/app/agentworker, internal/infrastructure/agentboot, internal/infrastructure/agenttransport/nats, internal/worktreerpc, cmd/archie-agent; MIGRATION.md row 5).
Maintainer decision: the archie-agent worker moves into the runner's sandbox rather than being deleted. Sandboxed agents are part of what Archie sells (risk, governance, security). Only its NATS transport goes (`internal/app/agentworker`, `internal/infrastructure/agentboot`, `internal/infrastructure/agenttransport/nats`, `internal/worktreerpc`, `cmd/archie-agent`; MIGRATION.md row 5).
Lifecycle cases specific to task runs, from the cross-check of the old task lifecycle (the general ones are #2036). Each needs to come across with the task-run kind:
Retry modes: refresh onto base, continue pushed work, and keep the worktree (the budget continue), with RequiresBranch refused when there is no branch (internal/taskstate).
Resume a retry whose worktree is gone (4e5b91d79); resume the task branch before acquiring a container (34f47a4bd).
Approval kinds: plan, review gate and budget; re-reviews counted against a cap under the row lock (RespondReviewGate).
Pull request states (open, merged, rejected), and a review that arrives during a remediation queued behind it and promoted when the remediation reaches pr_open (e0db40963).
Park pr_open on a permanent forge failure (a262151cb).
Refuse to run on the host: no container pool or task transport parks transient rather than running unsandboxed (parkCapabilityUnavailable).
Pre-run checks that park with a blocker and a link to the fix: workflow disabled, no execution identity, agent not assigned, policy denied, connection permit, repository, connection credential, forge extension, model credential, model credit.
Cancel and reject close the forge issue; abandon leaves it open (81862273c).
Worktrees: keep a terminal worktree with uncommitted or unpushed work (4e9b30d71, c98666d6b); reclaim idle clones hourly and when the volume is full (1d329bad3, 055f2da9c).
Park when the agent's container exits before replying, or reports no status (d01a3c464, 7b2af3348).
Lifecycle cases specific to task runs, from the cross-check of the old task lifecycle (the general ones are #2036). Each needs to come across with the task-run kind:
- Retry modes: refresh onto base, continue pushed work, and keep the worktree (the budget continue), with `RequiresBranch` refused when there is no branch (`internal/taskstate`).
- Resume a retry whose worktree is gone (4e5b91d79); resume the task branch before acquiring a container (34f47a4bd).
- Approval kinds: plan, review gate and budget; re-reviews counted against a cap under the row lock (`RespondReviewGate`).
- Pull request states (open, merged, rejected), and a review that arrives during a remediation queued behind it and promoted when the remediation reaches pr_open (e0db40963).
- Park pr_open on a permanent forge failure (a262151cb).
- Refuse to run on the host: no container pool or task transport parks transient rather than running unsandboxed (`parkCapabilityUnavailable`).
- Pre-run checks that park with a blocker and a link to the fix: workflow disabled, no execution identity, agent not assigned, policy denied, connection permit, repository, connection credential, forge extension, model credential, model credit.
- Cancel and reject close the forge issue; abandon leaves it open (81862273c).
- Worktrees: keep a terminal worktree with uncommitted or unpushed work (4e9b30d71, c98666d6b); reclaim idle clones hourly and when the volume is full (1d329bad3, 055f2da9c).
- Park when the agent's container exits before replying, or reports no status (d01a3c464, 7b2af3348).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Today archie picks up a forge issue, runs an agent in a sandboxed task container and commits through the daemon. #1978 and #2012 delete that path without a replacement, so the capability would disappear at slice 6.
Keep it as a document kind the engine executes: a task-triggered workflow whose agent runs in the runner's sandbox (profiles, egress allowlist, the network grant of #1968), whose brief goes in /.git/task.json, and whose commits and pushes are made by the daemon, never the model. The repo stays one optional input, so nothing else in the product assumes it.
Done when: an issue with a task label produces a run that ends in a commit or a pull request, shown in the dashboard like any other run.
Part of epic #1977. The dependency could not be recorded: this Gitea's dependency write endpoint answers 404 and the connector that used to add it is disconnected, so this comment carries the link.
Maintainer decision: the archie-agent worker moves into the runner's sandbox rather than being deleted. Sandboxed agents are part of what Archie sells (risk, governance, security). Only its NATS transport goes (
internal/app/agentworker,internal/infrastructure/agentboot,internal/infrastructure/agenttransport/nats,internal/worktreerpc,cmd/archie-agent; MIGRATION.md row 5).Lifecycle cases specific to task runs, from the cross-check of the old task lifecycle (the general ones are #2036). Each needs to come across with the task-run kind:
RequiresBranchrefused when there is no branch (internal/taskstate).4e5b91d79); resume the task branch before acquiring a container (34f47a4bd).RespondReviewGate).e0db40963).a262151cb).parkCapabilityUnavailable).81862273c).4e9b30d71,c98666d6b); reclaim idle clones hourly and when the volume is full (1d329bad3,055f2da9c).d01a3c464,7b2af3348).