Blog
Notes on coordinating one change across repositories, and on the parts of the problem that do not have a tidy answer yet.
A code graph for agents that spans repos and parallel features
Why ivar indexes the hall once and layers each feature on top, what the agent gets back from one query, and what that did to token use in a benchmark.
The context problem nobody solved: AI agents across multiple repos
An agent is good inside one repo and blind between them. Five workarounds, and where all of them stop.
Configure Figma MCP for OpenCode in one step
Ivar materialises the Figma MCP server config into every session automatically. No manual setup, no token management, no per-repo duplication.
How ivar helps non-technical teams work across multiple repos
You don't need to write code to benefit from ivar. It gives product managers, designers, and tech leads visibility into a multi-repo codebase — and lets AI agents do the heavy lifting.
Git worktrees are great. They stop at the repo boundary.
Everything the worktree posts get right, and the question that comes after it.