OpenCode + GitNexus: Give OpenCode Real Codebase Memory, Every Developer Use this

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: OpenCode + GitNexus: Give OpenCode Real Codebase Memory, Every Developer Use this
- URL: https://www.youtube.com/watch?v=bhsd9MXfccg
- Topic: Agent Architecture
- My current learning frame: Use GitNexus as a codebase memory layer for OpenCode: index the repository, expose targeted retrieval tools, and let the coding agent query project structure before editing.
- Why this matters: The atlas needs repeatable patterns for keeping agents grounded in real code instead of re-reading or guessing project context.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "Coding agents have one weakness that nobody really talks about. They read your code file by file. So, when you ask Cursor or Open Code or Claude Code to change one function, the agent looks at that function,..."
- 1:58 / Evidence 2: "runs inside Claude itself. It makes a mental graph of your code, and that graph lives in the conversation. It's good for one-off exploration, but it doesn't persist, and it doesn't expose tools to other agents. Git Nexus..."
- 4:19 / Evidence 3: "agent needs to actually reach for the graph instead of falling back to grep or read file. Without that line, sometimes the agent forgets the tools are even there. Next part is hooking it into Open Code. You..."
- 7:19 / Evidence 4: "you can chat with the code base directly in the browser. The chat panel uses a LangChain React agent that has access to the same MCP tools. So, you can ask things like, "What does the authentication flow..."
- 8:57 / Evidence 5: "But for solo devs and most teams, the open source version covers everything you actually need. One last tip. After you make commits, the index can go stale. If you're using Claude Code, the post tool use hook..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page agent harness map with tool boundaries and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Model -> Harness -> Tools -> Verifier -> Artifact
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "OpenCode + GitNexus: Give OpenCode Real Codebase Memory, Every Developer Use this", not a generic Agent Architecture essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.