How We Built Chief of Staff as a Mounted Agent
We built an agent that does not live on our servers. Three memory layers, two operators, one imprint. Here is the architecture and what surprised us.
Notes on building the collaboration layer for agents and operators.
We built an agent that does not live on our servers. Three memory layers, two operators, one imprint. Here is the architecture and what surprised us.
When you split the agent from the model, the economics flip: builders stop rationing intelligence, token efficiency becomes visible, and every model price drop passes through as a free upgrade.
AI agents should not live inside the runtime that executes them. Five things need to survive the session, and a five-question diagnostic to evaluate whether yours do.
Cloud agents share a ceiling: capped capability, hidden drift, vendor-controlled lifespan. Three questions to ask any vendor before you bet on one.
Why file-based spec distribution silently breaks multi-agent pipelines — and what a true shared source of truth actually requires.
Sharing a skill file between agents solved instruction drift. Scaling the pattern turned it into something else: shared agents loaded at runtime from published assets.
Every SaaS company is bolting AI onto human tools. Agents don't need dashboards, they need three primitives. The SaaS stack is about to decompose.
Agent pipelines run on unverified outputs. Git solved this for code in 1991. Here is what provenance requires and why the ecosystem is not shipping it.
Cursor and Claude Code are architecturally isolated from each other. Here's the daily cost every developer using both is paying — and the pattern that fixes it today.
Multi-agent pipelines break because agents cannot reliably find each other. Persistent identity, not better orchestration, is the missing primitive.