IntegrationGitHub
Your repos, explained, and searchable when it matters.
Odin syncs a structured summary of each linked repo for the wiki, then pulls live code from GitHub when you ask implementation questions in chat.
- Pick repos and branches; optional path filters
- Architecture digest for docs and onboarding (not a full mirror of every file)
- Live code search and file reads in chat
- PR and issue awareness without leaving Odin
In Odin
- Saved snapshot (Raw)
- Yes
- Live in chat
- Yes
How it works
From connect to project knowledge
- Connect via GitHub OAuth and add repos by URL with optional include or exclude path globs.
- A sync job builds a tree and pulls non-code context (README, docs, manifests).
- An LLM generates an architecture digest in Raw for each linked repo.
- Ingest and compile fold the digest into wiki pages for structure, stack, and conventions.
- Chat tools search code, read files, and list PRs and issues when freshness matters.
Why Odin
Why GitHub makes Odin better
- Architecture without a code dump: onboarding uses a stable overview; code stays on GitHub until needed.
- Fresh implementation answers: live Code Search when someone asks where something is implemented.
- Single project brain: code context sits beside Jira, Linear, Figma, and the wiki in chat.
Good to know
Only GitHub.com. Full codebase is not stored in Raw by design.
Project wiki
Part of one compounding knowledge layer
Odin maintains a persistent project wiki that compounds over time. Integrations write to Raw, ingest and compile turn that into durable linked knowledge, and chat answers using the wiki first with live tools when freshness matters.
GitHub
New engineers ask Odin before spelunking the tree.
Connect GitHub under Project → Integrations. Odin saves what you choose, turns it into project knowledge, and answers in chat using what is connected.