Multi-repo workspaces: coordinating agents across boundaries
How we built workspace support that lets agents coordinate changes across multiple repositories.
Most real-world features span multiple repositories. A new API endpoint means changes to the backend, frontend, shared types, and maybe infrastructure. kill9 workspaces let agents coordinate across all of them.
The problem
Traditional AI coding tools work in a single repository context. But modern software is distributed. A feature might touch three repos, each with its own CI pipeline, branch strategy, and review process.
Worktrees
Every initiative in kill9 gets its own worktree — an isolated branch that doesn't interfere with other work. When agents work across repos, each repo gets its own worktree, all linked to the same initiative.
Coordination
The orchestrator ensures agents working across repos share context. If the backend agent changes an API signature, the frontend agent knows immediately. Type changes propagate. Integration tests run across boundaries.
Zero conflicts
Because each initiative is isolated in its own worktree, there's no stashing, no "works on my branch" problems, no coordination overhead. Five features can build in five branches simultaneously, all clean.