---
title: "#cross-repo-context articles | Hashnode"
description: "Explore 7 articles tagged #cross-repo-context on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/cross-repo-context"
---

Tag

# #cross-repo-context

7 posts · 0 followers

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 31](https://hashnode.com/posts/repo-access-was-never-the-hard-part/6a1bf19820665204d4f927e0)

### [Repo access was never the hard part](https://riftmap.hashnode.dev/repo-access-was-never-the-hard-part?utm_source=hashnode&utm_medium=feed)

The multi-repo agent race is solving repository access. But access is plumbing — the cross-repo dependency graph is the part nobody upstream is parsing.

8 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/repo-access-was-never-the-hard-part?utm_source=hashnode&utm_medium=feed)

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 30](https://hashnode.com/posts/inferred-context-is-not-a-dependency-graph/6a1b4bd9860ed170819d09da)

### [Inferred context is not a dependency graph](https://riftmap.hashnode.dev/inferred-context-is-not-a-dependency-graph?utm_source=hashnode&utm_medium=feed)

An enterprise context engine makes your agent generate better code. A parsed dependency graph is the thing you gate a deploy on. Two jobs, two kinds of machinery, and why a confidence score is the wrong guarantee for the second one.

16 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/inferred-context-is-not-a-dependency-graph?utm_source=hashnode&utm_medium=feed)

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 23](https://hashnode.com/posts/symbol-graphs-and-artifact-graphs-why-sourcegraph-stops-where-infrastructure-starts/6a11659bda3f42d25f332702)

### [Symbol graphs and artifact graphs: why Sourcegraph stops where infrastructure starts](https://riftmap.hashnode.dev/symbol-graphs-and-artifact-graphs-why-sourcegraph-stops-where-infrastructure-starts?utm_source=hashnode&utm_medium=feed)

Why Sourcegraph's symbol graph can't tell you who consumes your Helm chart at v3.2.0 — and why symbol graphs and artifact graphs are different categories.

22 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/symbol-graphs-and-artifact-graphs-why-sourcegraph-stops-where-infrastructure-starts?utm_source=hashnode&utm_medium=feed)

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 20](https://hashnode.com/posts/cross-repo-context-is-in-product-docs-the-graph-is-not/6a0db547b1ed7bce01da6e16)

### [Cross-repo context is in product docs. The graph is not](https://riftmap.hashnode.dev/cross-repo-context-is-in-product-docs-the-graph-is-not?utm_source=hashnode&utm_medium=feed)

The vocabulary moved into vendor docs in sixty days. The parser-derived cross-repo dependency graph it describes hasn't shipped in any AI coding product.

17 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/cross-repo-context-is-in-product-docs-the-graph-is-not?utm_source=hashnode&utm_medium=feed)

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 13](https://hashnode.com/posts/you-don-t-need-a-virtual-monorepo-you-need-a-graph/6a0436b2402794c859b5e329)

### [You don't need a virtual monorepo. You need a graph.](https://riftmap.hashnode.dev/you-don-t-need-a-virtual-monorepo-you-need-a-graph?utm_source=hashnode&utm_medium=feed)

Two patterns for AI coding agent context across repos. One scales by hand, one by construction.

16 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/you-don-t-need-a-virtual-monorepo-you-need-a-graph?utm_source=hashnode&utm_medium=feed)

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 12](https://hashnode.com/posts/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves/6a02e5246a2561e6c739131f)

### [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.

12 min read · [riftmap.hashnode.dev](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)

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

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 10](https://hashnode.com/posts/meta-needed-50-ai-agents-to-map-their-tribal-knowledge-the-most-durable-piece-of-their-stack-is-the-part-you-can-build-today/6a008aefe3eebc2e20845c71)

### [Meta needed 50+ AI agents to map their tribal knowledge. The most durable piece of their stack is the part you can build today.](https://riftmap.hashnode.dev/meta-needed-50-ai-agents-to-map-their-tribal-knowledge-the-most-durable-piece-of-their-stack-is-the-part-you-can-build-today?utm_source=hashnode&utm_medium=feed)

Three teams shipped the same diagnosis in two weeks: AI coding agents need cross-repo context.

11 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/meta-needed-50-ai-agents-to-map-their-tribal-knowledge-the-most-durable-piece-of-their-stack-is-the-part-you-can-build-today?utm_source=hashnode&utm_medium=feed)
