A CLI experiment to reduce coding agent context in multi-repo work
The main problem is how to measure and reason about token and context use when work across a project split into several . A CLI called knit treats several as one project. It creates “bundles” that connect related branches and worktrees across those .
The CLI moves the work into a clean directory with the needed in the right worktree state. It also helps with cross-repo commits, conflict checks, , and similar tasks. Because do not know this workflow by default, knit can include AGENTS.md files at the project level and bundle level.
In version v0.1.0-alpha.3, it adds guidance for when an agent should spawn a subagent for work that stays inside one . The goal is to see whether this reduces irrelevant context for each agent and improves token use and .
Key points
- knit is a CLI for handling several as one project.
- Bundles connect related branches and worktrees across .
- The tool prepares a clean directory so agents can work with the right loaded.
- AGENTS.md files give project-level and bundle-level instructions to .
- may help reduce irrelevant context when a task only affects one .