The chat agent has only memory_edit and skill_activate, so it cannot act on the codebase. cfg.Tools.MCPServers + the stdio transport are the designed extension point (configuredMCPProvider in cmd/archied/main.go already builds providers from config). Sam's requirement is to expose specific capabilities narrowly rather than granting host access, and he has a Firecracker sandbox POC at /work/clones/gorev (firecracker/sandbox) intended for exactly this.
Acceptance Criteria
MCP servers are configurable per deployment and discovered into the chat agent tool loop. A narrowly scoped code MCP server runs in the daemon container against an explicitly configured workspace and can make a code change end to end. Firecracker execution remains a requirement tracked separately in archie-core-abg.17.44.
Notes
Design: docs/prds/mcp-tool-completion.md#sandboxed-mcp-tool-servers-for-the-chat-agent-178-and-firecracker-substrate-179. Reuses internal/container.Pool, not a new sandbox mechanism. Suggested council lenses: lens-operator, lens-deletionist.
Close reason
Closed on GitHub; syncing bead state
Imported from beads archie-core-1786637494450-178-67d1e003 · GitHub #199 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-26
The chat agent has only memory_edit and skill_activate, so it cannot act on the codebase. cfg.Tools.MCPServers + the stdio transport are the designed extension point (configuredMCPProvider in cmd/archied/main.go already builds providers from config). Sam's requirement is to expose specific capabilities narrowly rather than granting host access, and he has a Firecracker sandbox POC at /work/clones/gorev (firecracker/sandbox) intended for exactly this.
### Acceptance Criteria
MCP servers are configurable per deployment and discovered into the chat agent tool loop. A narrowly scoped code MCP server runs in the daemon container against an explicitly configured workspace and can make a code change end to end. Firecracker execution remains a requirement tracked separately in archie-core-abg.17.44.
### Notes
Design: docs/prds/mcp-tool-completion.md#sandboxed-mcp-tool-servers-for-the-chat-agent-178-and-firecracker-substrate-179. Reuses internal/container.Pool, not a new sandbox mechanism. Suggested council lenses: lens-operator, lens-deletionist.
### Close reason
Closed on GitHub; syncing bead state
---
_Imported from beads `archie-core-1786637494450-178-67d1e003` · GitHub #199 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-26_
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.
The chat agent has only memory_edit and skill_activate, so it cannot act on the codebase. cfg.Tools.MCPServers + the stdio transport are the designed extension point (configuredMCPProvider in cmd/archied/main.go already builds providers from config). Sam's requirement is to expose specific capabilities narrowly rather than granting host access, and he has a Firecracker sandbox POC at /work/clones/gorev (firecracker/sandbox) intended for exactly this.
Acceptance Criteria
MCP servers are configurable per deployment and discovered into the chat agent tool loop. A narrowly scoped code MCP server runs in the daemon container against an explicitly configured workspace and can make a code change end to end. Firecracker execution remains a requirement tracked separately in archie-core-abg.17.44.
Notes
Design: docs/prds/mcp-tool-completion.md#sandboxed-mcp-tool-servers-for-the-chat-agent-178-and-firecracker-substrate-179. Reuses internal/container.Pool, not a new sandbox mechanism. Suggested council lenses: lens-operator, lens-deletionist.
Close reason
Closed on GitHub; syncing bead state
Imported from beads
archie-core-1786637494450-178-67d1e003· GitHub #199 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-26