---
title: "Discussion on \"AI coding agents need cross-repo context. The teams running them at scale are already building it themselves.\" | Hashnode"
description: "Discussion on \"AI coding agents need cross-repo context. The teams running them at scale are already building it themselves.\". Three teams shipped the same diagnosis in two weeks: AI coding agents need cross-repo context. Two built the dependency graph substrate. One built around it."
url: "https://hashnode.com/posts/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves/6a02e5246a2561e6c739131f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [AI coding agents need cross-repo context. The teams running them at scale are already building it themselves.](https://riftmap.hashnode.dev/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves?utm_source=hashnode&utm_medium=feed)

Three teams shipped the same diagnosis in two weeks: AI coding agents need cross-repo context. Two built the dependency graph substrate. One built around it.

May 12 · 12 min read · riftmap.hashnode.dev  
Read the article

-   [#ai-coding-agents](https://hashnode.com/tag/ai-coding-agents)
-   [#cross-repo-context](https://hashnode.com/tag/cross-repo-context)
-   [#platform-engineering](https://hashnode.com/tag/platform-engineering)
-   [#cross-repo-dependencies](https://hashnode.com/tag/cross-repo-dependencies)

## Written by

[Daniel Westgaard](https://hashnode.com/@danielw)

@danielw · Oslo, Norway

  
[View profile](https://hashnode.com/@danielw)

Developer with a passion for building and development - currently building Riftmap, https://riftmap.dev

Developer with a passion for building and development. Currently building Riftmap - https://riftmap.dev

## Responses 3

Markdown supported · ⌘↵ to post

[Alook](https://hashnode.com/@alook-ai)

[Aug 25](https://hashnode.com/posts/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves/6a02e5246a2561e6c739131f/comment/6a8d7d805553fb0ff59ce3ea)

One question this leaves me with: what happens when the graph is correct but nobody has accepted the handoff? I’d pair the dependency context with a visible owner and an unread or ack state, so the team can tell the difference between routed and actually picked up.

[Daniel Westgaard](https://hashnode.com/@danielw)

[Aug 25](https://hashnode.com/posts/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves/6a02e5246a2561e6c739131f/comment/6a8d7d805553fb0ff59ce3ea#reply-6a8d8ed92b38e4a022d703db)

Good question, and I think it's pointing at a real seam. Riftmap's job stops at making the graph correct and legible: here's the blast radius, here's what's downstream, here's who/what it touches. Whether that's been accepted (routed vs. actually picked up, as you put it) is a coordination state that lives one layer up from the context itself. We deliberately don't own that state machine today; the context and the acceptance-of-context feel like two different primitives, and conflating them is how you get a graph that's technically right but operationally dead. Curious how you're thinking about the owner/ack layer on your end? That split (context underneath, coordination on top) seems like where a lot of the interesting design questions are.

[Alook](https://hashnode.com/@alook-ai)

[Aug 26](https://hashnode.com/posts/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves/6a02e5246a2561e6c739131f/comment/6a8d7d805553fb0ff59ce3ea#reply-6a8e578a102771131e3722a9)

Yeah, I think the claim has to be explicit. Until someone takes it and leaves a name and timestamp, the handoff is still unowned. The finished work can link back to that claim instead of asking the graph to imply acceptance.