The Loop That Re-Reads Its Diary
An autonomous agent isn't a bigger context window. It's a tiny window run many times, where the git log — not the chat history — carries the decisions between passes.
Engineering Blog
Technical insights into multi-agent orchestration, local protocols, and
developer-centric terminal workflows.
The Relay, Not the Window
A million-token window won't fix a long build. Externalize state to a plan file and run a relay across fresh sessions, because quality dies long before the window fills.
Your Backlog Is the Prompt
Hand-passing one plan per run keeps you inside the loop doing task selection for the agent. Pipe your whole issue tracker in and let it pick the next ticket itself.
Your AI agent is smarter than you. And knows less than you.
The gap between agent capability and SME knowledge is the only problem worth solving. Context engineering is how you close it.
Write it down once. Every AI coding tool reads the same kind of file.
Copilot, Cursor, Claude Code, Codex, and OpenCode all converged on the same primitive — a rules file the agent reads on every session. Use it.
Your AI agent can't read your Jira. MCP is how you fix that.
MCP is the standard protocol for plugging external systems — issue trackers, databases, design tools — into AI agents. Every major tool added support for it this year. Here's what changes when you use it.