Decision: one task runtime, Kit or the default container path #1865

Closed
opened 2026-11-12 09:34:38 +00:00 by sam · 2 comments
Owner

Problem

A task runs one of two ways. daemon.go runs it as a Kit task when its agent profile sets kit (AgentProfile.IsKit), and otherwise through ContainerPool.Acquire. Each path has its own run flow, container start, worker environment, network setup and State Store relay. Only the Kit path gets the internal sandbox bridge and the egress relay. The maintainer has not run a Kit task yet.

Decide

Pick one runtime and delete the other:

  • Kit only. Default tasks become a built-in Kit. The default container path, its env builder and the in-process State Store relay go.
  • Default path only. Kit support goes. The sandbox bridge and egress relay move onto the default path.

Done when

The choice is recorded here, and the follow-up consolidation issues are re-scoped to it.

Related: #1864.

## Problem A task runs one of two ways. `daemon.go` runs it as a Kit task when its agent profile sets `kit` (`AgentProfile.IsKit`), and otherwise through `ContainerPool.Acquire`. Each path has its own run flow, container start, worker environment, network setup and State Store relay. Only the Kit path gets the internal sandbox bridge and the egress relay. The maintainer has not run a Kit task yet. ## Decide Pick one runtime and delete the other: - **Kit only.** Default tasks become a built-in Kit. The default container path, its env builder and the in-process State Store relay go. - **Default path only.** Kit support goes. The sandbox bridge and egress relay move onto the default path. ## Done when The choice is recorded here, and the follow-up consolidation issues are re-scoped to it. Related: #1864.
Author
Owner

Correction to the framing above. Per the external-agent-harness PRD, the two paths are not two copies of one thing. An image profile runs the built-in ai-sdk agent loop with the network its identity is granted. A Kit profile runs an external CLI (Claude Code, Codex and others) on the proxied egress path. "Kit only" would mean packaging the built-in loop as a Kit, and image-profile workflows that need raw DNS, ICMP or TCP (the firewall investigator) would lose that. The real choice is narrower: keep both runner types, but share one container start, env builder and relay (#1868, #1869, #1870). The NATS scoping in #1866 applies to both either way.


Generated by Claude Code

Correction to the framing above. Per the external-agent-harness PRD, the two paths are not two copies of one thing. An image profile runs the built-in ai-sdk agent loop with the network its identity is granted. A Kit profile runs an external CLI (Claude Code, Codex and others) on the proxied egress path. "Kit only" would mean packaging the built-in loop as a Kit, and image-profile workflows that need raw DNS, ICMP or TCP (the firewall investigator) would lose that. The real choice is narrower: keep both runner types, but share one container start, env builder and relay (#1868, #1869, #1870). The NATS scoping in #1866 applies to both either way. --- _Generated by [Claude Code](https://claude.ai/code)_
Author
Owner

Decided: Archie keeps its own agent loop only, and Kit plus external harness support is deleted. Tracked in #1877.


Generated by Claude Code

Decided: Archie keeps its own agent loop only, and Kit plus external harness support is deleted. Tracked in #1877. --- _Generated by [Claude Code](https://claude.ai/code)_
sam closed this issue 2026-11-12 09:48:57 +00:00
sam added the highdecision labels 2026-11-12 15:51:30 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1865