A Kit task's container gets the daemon's own NATS credential (daemon kit_task.go passes ConnectedNATS.Token into the worker env), and the model's tools run in that container. That breaks the invariant that the daemon's credentials never enter an agent container: code in a task can publish on any subject, including the forge RPC (comment, close, create PR on any repository with the daemon's forge credential) and the task queue. Done when a container's NATS credential can only reach the subjects of its own task.
Close reason
4699280c: on the embedded broker a container logs in as task- with its run credential; archied checks it with the State Store and grants only that task's handoff, log, event, forge and push subjects and its own inbox. Containers no longer receive the broker token. External mode is unchanged and reported as a health issue; scoping it is filed separately.
Imported from beads archie-core-6fsg · GitHub #1410 · type bug · priority P1 · created 2026-10-04 · closed 2026-10-04
A Kit task's container gets the daemon's own NATS credential (daemon kit_task.go passes ConnectedNATS.Token into the worker env), and the model's tools run in that container. That breaks the invariant that the daemon's credentials never enter an agent container: code in a task can publish on any subject, including the forge RPC (comment, close, create PR on any repository with the daemon's forge credential) and the task queue. Done when a container's NATS credential can only reach the subjects of its own task.
### Close reason
4699280c: on the embedded broker a container logs in as task-<id> with its run credential; archied checks it with the State Store and grants only that task's handoff, log, event, forge and push subjects and its own inbox. Containers no longer receive the broker token. External mode is unchanged and reported as a health issue; scoping it is filed separately.
---
_Imported from beads `archie-core-6fsg` · GitHub #1410 · type bug · priority P1 · created 2026-10-04 · closed 2026-10-04_
sam
added the highbug labels 2026-10-27 13:39:01 +00:00
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.
A Kit task's container gets the daemon's own NATS credential (daemon kit_task.go passes ConnectedNATS.Token into the worker env), and the model's tools run in that container. That breaks the invariant that the daemon's credentials never enter an agent container: code in a task can publish on any subject, including the forge RPC (comment, close, create PR on any repository with the daemon's forge credential) and the task queue. Done when a container's NATS credential can only reach the subjects of its own task.
Close reason
4699280c: on the embedded broker a container logs in as task- with its run credential; archied checks it with the State Store and grants only that task's handoff, log, event, forge and push subjects and its own inbox. Containers no longer receive the broker token. External mode is unchanged and reported as a health issue; scoping it is filed separately.Imported from beads
archie-core-6fsg· GitHub #1410 · type bug · priority P1 · created 2026-10-04 · closed 2026-10-04