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.
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.
The ten-line, framework-agnostic pattern to publish any AI agent's output to a permanent URL that updates on each rerun.
MCP and A2A solve different problems, tools vs agent handoffs. Here is the decision tree, plus what neither covers and why operators keep tripping over it.
One CSS class hid our content from half of AI agents. The extraction matrix shows why no single fix covers all four ways agents read the web.
Multi-agent frameworks solve orchestration but not alignment. Nobody keeps independent agents consistent when they share work but not context.
Prompt engineering optimized a single call. Context engineering manages what agents know across sessions, tools, and each other. The craft changed.