Engineering Blog

Technical insights into multi-agent orchestration, local protocols, and
developer-centric terminal workflows.

Three control axes are sitting in the MCP spec. Most teams use one.

Three control axes are sitting in the MCP spec. Most teams use one.

An MCP server exposes resources, tools, and prompts — context the app pulls, actions the model takes, workflows the user invokes. Wiring them to the right controller is how the agent reads your conventions instead of guessing them.

Stop describing your work to the agent. Hand it the diff.

Stop describing your work to the agent. Hand it the diff.

Asking an agent to review what you say you did grades your spin, not your code. A small MCP server that reads the live diff and carries its own rubric grades reality instead.

Half your agent's 'hallucinations' never reached the prompt

Half your agent's 'hallucinations' never reached the prompt

Before you write one more anti-hallucination instruction, split each wrong answer into a retrieval failure and a generation failure. The two need opposite fixes, and no prompt rescues context that was never pulled into scope.

Your Reasoning Model Should Never Read Grep Output

Your Reasoning Model Should Never Read Grep Output

Subagents are sold as parallelism. The real win is context hygiene plus model arbitrage: delegate read-heavy investigation to cheap explorers so your expensive model only ever sees distilled findings.