Firecracker substrate for sandboxed MCP code tools #704

Closed
opened 2026-10-27 13:37:24 +00:00 by sam · 0 comments
Owner

Replace the interim daemon-container code MCP execution path with a real Firecracker boundary. Extend or extract the gorev POC to support a long-lived bidirectional guest process, explicit workspace import/export, per-turn filesystem checkpoints, lifecycle/health, and concurrent-instance-safe networking. Then adapt the MCP provider launcher without changing the chat/tool contract.

Acceptance Criteria

MCP server code and tool execution occur inside a Firecracker VM; the guest cannot access daemon-host files outside the imported workspace; changes export deterministically; pre-change checkpoints support /restore; lifecycle cleanup survives crashes; tests prove the configured provider cannot silently fall back to host execution.

Close reason

Decided in docs/prds/mcp-tool-completion.md#sandboxed-mcp-tool-servers-for-the-chat-agent-178-and-firecracker-substrate-179: not built now. Sandboxed MCP servers (#178) reuse the existing Docker-backed internal/container.Pool; Firecracker becomes a second backend behind the same acquire/release contract only if a measured escape/isolation gap against Docker-backed sandboxing shows up in production. Reopen if that evidence appears.


Imported from beads archie-core-1786637494482-179-e23fe15a · GitHub #200 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-19

Replace the interim daemon-container code MCP execution path with a real Firecracker boundary. Extend or extract the gorev POC to support a long-lived bidirectional guest process, explicit workspace import/export, per-turn filesystem checkpoints, lifecycle/health, and concurrent-instance-safe networking. Then adapt the MCP provider launcher without changing the chat/tool contract. ### Acceptance Criteria MCP server code and tool execution occur inside a Firecracker VM; the guest cannot access daemon-host files outside the imported workspace; changes export deterministically; pre-change checkpoints support /restore; lifecycle cleanup survives crashes; tests prove the configured provider cannot silently fall back to host execution. ### Close reason Decided in docs/prds/mcp-tool-completion.md#sandboxed-mcp-tool-servers-for-the-chat-agent-178-and-firecracker-substrate-179: not built now. Sandboxed MCP servers (#178) reuse the existing Docker-backed internal/container.Pool; Firecracker becomes a second backend behind the same acquire/release contract only if a measured escape/isolation gap against Docker-backed sandboxing shows up in production. Reopen if that evidence appears. --- _Imported from beads `archie-core-1786637494482-179-e23fe15a` · GitHub #200 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-19_
sam added the mediumfeature labels 2026-10-27 13:37:24 +00:00
sam self-assigned this 2026-10-27 13:37:24 +00:00
sam closed this issue 2026-10-27 13:37:24 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#704