Agents Overview

Every Boring Infra Co. product is designed to work alongside AI coding agents — not replace them. Here is how each tool fits into agent workflows.

JSON-first CLIs

Root and Sandman support --json on every command for structured agent automation. Meno ships --json on status, verify, and inspect as a frozen v1 contract.

root plan install terraform --json
sandman create demo --ttl 2h --json
meno status --json

Agents can parse output, make decisions, and chain commands without scraping human-readable text.

MCP integration

Combie and Meno expose context to agents via Model Context Protocol. Pico’s MCP is planned.

Product	MCP tools	Mode
Combie	5 read-only tools	combie mcp via stdio
Pico	history, diff	Planned / foundation
Meno	verification state, submit evidence, request evaluation	meno connect --adapter agent --stdio

Set up Combie for agents:

combie agent setup

This configures Cursor, Claude Code, and Codex automatically.

Agent skill packs

Root ships skill packs for popular agents:

• Codex
• Claude Code
• Cursor
• Generic agent

See the Root skills directory on GitHub.

Combie offers a composition skill:

npx skills add BoringInfraCo/combie --skill combie -a cursor -a claude-code -a codex

Verification state (Meno)

Meno is the check before an agent declares work complete. Verdicts come from evaluation, never from agent prose.

meno status --json
# gather evidence with project tests / Playwright / commands
meno verify --json
meno connect --adapter agent --stdio

Rules agents must follow:

1. Inspect Meno before calling work done
2. Treat unknown as unknown — never as proven
3. Gather evidence with project tools; do not invent verdicts
4. Human confirmation is meno inspect --confirm, not MCP
5. Do not weaken, rewrite, or delete frozen claims to obtain proven

Cross-agent work continuity

Harnie bridges agent harnesses. When one agent finishes work and another needs to continue:

harnie import pi session.jsonl
harnie handoff work:pi:abc --to opencode

A shared place to work (Campfire)

Campfire is for the moment when more than one person or agent is involved. The goal, the changes, the findings, and the decisions live in one workspace so nobody has to reconstruct what happened from three different agent sessions.

Campfire doesn’t replace Codex, Claude Code, OpenCode, or Harnie. It doesn’t orchestrate your agents. It gives them someplace to gather.

campfire workspace create billing-flow
campfire goal "Ship the new billing flow"
campfire status

Agent bundles (Root)

Transfer agent working configuration between machines — same agent, no credentials in the bundle:

root agent-bundle export codex
root agent-bundle apply ./bundle.tar.gz

Recommended agent workflows

Task	Tools
Set up agent tooling	Root
Spin up test infrastructure	Sandman
Give agent stack context	Combie MCP
Audit agent security	Pico
Hand off between agents	Harnie
Give the team and its agents one place to work	Campfire
Bind evidence to this subject	Meno

Local-first for agents

Agents operate on local state — no API keys for Boring Infra services, no rate limits on our side, no data leaving your machine unless you explicitly sync to your own cloud accounts (Sandman only).