Originally published on AI Tech Connect.
What changes when a task spans more than one repository A coding agent working inside a single git checkout has a genuinely easy job by comparison: it can grep the whole tree, follow an import to its definition, and trust that anything it sees on disk is the current, canonical version. None of that holds once a task needs a services repo, the shared library that repo imports, and the infra repo that deploys it. The agent's context window still has room for the work; what it is missing is a map of where the rest of the truth lives. Context windows are not the bottleneck most teams think they are. Even a modest context window comfortably holds a manifest, a repo map and the working set for one repo. The bottleneck is that nobody told the agent a second and third repo exist. Cross-repo…
Top comments (0)