Blog
Notes on coordinating one change across repositories, and on the parts of the problem that do not have a tidy answer yet.
One MCP config for Claude Code, OpenCode and OMP
Each harness keeps MCP servers in its own file and logs in its own way. Declare a server once, write all three configs, and see where each login breaks.
One feature, three repos: a walkthrough
Promote the API and web app, discover the shared types need a change too, and deliver all three pull requests from one feature.
One repo, many agents: parallel features from a Figma prototype
Split a large prototype into subfeatures, run one agent per slice on its own branch with Figma MCP ready, and ship it as one pull request.
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.
Figma MCP on OpenCode: fix "Authentication failed"
Add the Figma MCP server to OpenCode in four commands. Why opencode mcp auth figma prints "Authentication failed", and how to get past it.
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.