Repository navigation
Releases
Eyrie 0.2.0
Eyrie 0.2.0: the view from above, for you and your coding agents
A live architecture map of your codebase that updates as you, or your coding agent, change the code.
Your agent just changed six files. What actually moved? Eyrie answers that: it parses your repository on your machine, builds a code knowledge graph, and shows it as an interactive map that stays in sync with the source. The same map is served to coding agents over MCP, so they can ask what an edit will break before making it, and what moved after it.
Submitted to the Meta Global AI Developer Hackathon (Indie Developer track).
🎬 Demo video: YouTube
Download
Eyrie 0.2.0 for macOS (Apple silicon and Intel), Windows (x64) and Linux (x64 and arm64).
| System | File |
|---|---|
| macOS, Apple silicon | Eyrie-0.2.0-arm64.dmg (or .zip) |
| macOS, Intel | Eyrie-0.2.0-x64.dmg (or .zip) |
| Windows, x64 | Eyrie-0.2.0-x64-Setup.exe |
| Debian, Ubuntu | eyrie-desktop_0.2.0_amd64.deb or _arm64.deb |
| Fedora, openSUSE | eyrie-desktop-0.2.0-1.x86_64.rpm or .arm64.rpm |
These builds are not signed by Apple or Microsoft. The first time you open Eyrie:
- macOS: open it once, then choose Open Anyway in System Settings → Privacy & Security.
- Windows: when SmartScreen stops the installer, choose More info → Run anyway. No administrator rights needed.
- Linux:
sudo apt install ./eyrie-desktop_0.2.0_amd64.deborsudo dnf install ./eyrie-desktop-0.2.0-1.x86_64.rpm, then open Eyrie from your applications menu.
Then add a repository folder (or drop one on the window) and open it to see its map.
Check your download: every file's SHA-256 is in SHA256SUMS, and GitHub records which build of this repository produced it:
shasum -a 256 -c SHA256SUMS --ignore-missing
gh attestation verify Eyrie-0.2.0-arm64.dmg --repo eyrie-hq/eyrieBuilt during the Meta hackathon (Oct 26 – Nov 4)
Eyrie's map, live graph and MCP server existed before the event. This is what was built during it:
- Meta's models in Eyrie. Muse is one of Eyrie's four AI backends: Eyrie runs the Muse CLI in an empty temporary folder with writing, shell commands and web access turned off, so the model can read nothing else and change nothing. The Meta Model API works through Eyrie's OpenAI-compatible backend (
--ai openaiwithEYRIE_OPENAI_BASE_URLpointed at it). - Ask the map. Ask a question in plain English and get numbered steps that cite components. The model may only call Eyrie's read-only graph tools and cannot read your code. Any step that cites something the tools did not return is rejected rather than shown. Pick who answers per question: Claude Code, Codex, Muse or an OpenAI-compatible API such as the Meta Model API.
- Health. Eight deterministic security rules over the graph, with no model involved, including three no file-by-file scanner can express: a public route that reaches a database write with no auth guard on the path, a server-only variable read in UI code, and a webhook that never verifies its signature.
- Recent work. When an agent records its task with
record_intent, Eyrie shows what it changed (+new,~changed) and why, and links the session to its commit through theCo-Authored-Bytrailer. - One
eyriecommand that opens the map, serves it to agents (eyrie mcp) and tells them it's there (eyrie init-agents), shipped inside the desktop app. - The insight drawer (
A) that holds Ask, Health and Recent and marks the map without leaving your lens. - Eight more languages, built with Muse Code: Kotlin, Swift, C, C++, Dart, Vue, Objective-C and Lua, bringing Eyrie to 16 languages.
Everything in 0.2.0
The live map
- Live, not generated. On every save, only the changed files are re-parsed, plus the files that depend on them if their exports changed. The diff animates into the map: new components get a green
+, edited ones a yellow~, removed ones a red−. Layout stays stable. - Change tape. Every save becomes a tick at the bottom of the screen; hover to light up what it touched, click to jump there. A recorded agent session sits on a shaded band.
- Nothing is guessed. Every relationship comes from static analysis (tree-sitter), and every edge carries a confidence.
Four lenses, plus 3D
- System (
1): the whole territory in one view: UI, API, services and data, plus every outside service found from the imports (50+ SDKs, such as Stripe, OpenAI, Algolia and Supabase). - Architecture (
2): every component in its lane, in request order: UI → Edge → API → Logic → Data → External. A missing API route is drawn in red. - Data flow (
3): who reads and who writes, with every link coloured by what it carries. - Sequence (
4): one request as lifelines, from the first handler down to the data, each message linked to the file and line that makes the call. - 3D city (
V): the same graph as a city where every building is a component and its height is lines of code.
Understand a component
- Details panel: what it does, its source with a code preview, Open in editor, what it calls, what uses it and the symbols inside.
- Trace and Impact: follow a request through everything a component calls, or see everything that could break if it changes.
- Search (
⌘Kor/), category filters andFto fit.
Insights (A)
- Ask the map, Health and Recent, as described above.
For coding agents (MCP)
- 12 tools answering from the same live graph:
architecture_overview,find_components,explain_component,impact,trace,find_path,components_for_files,recent_changes,record_intent,commit_history,checkandask. - Connect Coding Agents in a project's ⋯ menu sets up Claude Code, Codex, Gemini CLI or Cursor for you. GitHub Copilot (VS Code), Muse Code and any other MCP client take the same command:
claude mcp add eyrie -- eyrie mcp /path/to/your/repoeyrie init-agentsadds a short section toAGENTS.mdtelling agents to check impact before editing and what changed after. It's the only thing Eyrie ever writes into your repository.
Commit history and AI notes
- Eyrie records each new commit with the components it touched and any coding agent in its
Co-Authored-Bytrailer. - Optionally, an AI backend notes each commit: what it is for, whether the change matches its message, and its architectural risk. Every note must cite something the commit actually touched, or it is rejected.
16 languages
TypeScript/JavaScript, Python, Go, Java, C#, PHP, Ruby, Rust, Kotlin, Swift, C, C++, Dart, Vue, Objective-C and Lua, with routes, data models and external services detected across the common frameworks (Next.js, Express, FastAPI, Django, Spring, ASP.NET, Laravel, Rails, axum and more). JavaScript (Next.js, Node.js) has the deepest support.
Private by default
- No account. No telemetry. No server of its own. With AI off (the default), nothing leaves your machine.
- With AI on, Eyrie sends component names, commit messages and changed file paths to the backend you chose, under your own account, never your source code.
- The local server binds to
127.0.0.1with a random per-run token. The MCP server talks only to the agent that started it, over stdio.
Known limitations
- Builds are unsigned and there are no automatic updates yet: download the new version and install over the old one; your projects stay.
- Resolution is syntactic, so dynamic dispatch and dependency injection can be missed.
- Health is eight rules, not a full scanner.
@eyrie-hq/cliis not on npm yet: use theeyriecommand the desktop app installs.
Full details in the README.
License: AGPL-3.0. Free and open source.
gh attestation verify <file> --repo eyrie-hq/eyrie
Built from e149adf by https://github.com/eyrie-hq/eyrie/actions/runs/41887205183. The source of exactly this build is the tag's source archive below.
Eyrie 0.1.0-rc.2
Eyrie 0.1.0-rc.2 for macOS (Apple silicon and Intel), Windows (x64) and Linux (x64 and arm64).
These builds are not signed by Apple or Microsoft. The first time you open Eyrie:
- macOS: open it once, then choose Open Anyway in System Settings → Privacy & Security.
- Windows: when SmartScreen stops the installer, choose More info → Run anyway.
Check a download against SHA256SUMS, or check where it was built:
gh attestation verify <file> --repo eyrie-hq/eyrie
Built from 361141e by https://github.com/eyrie-hq/eyrie/actions/runs/39892049161. The source of exactly this build is the tag's source archive below.
Eyrie 0.1.0-rc.1
Eyrie 0.1.0-rc.1 for macOS (Apple silicon and Intel), Windows (x64) and Linux (x64 and arm64).
These builds are not signed by Apple or Microsoft. The first time you open Eyrie:
- macOS: open it once, then choose Open Anyway in System Settings → Privacy & Security.
- Windows: when SmartScreen stops the installer, choose More info → Run anyway.
Check a download against SHA256SUMS, or check where it was built:
gh attestation verify <file> --repo eyrie-hq/eyrie
Built from 3279f69 by https://github.com/eyrie-hq/eyrie/actions/runs/39889980930. The source of exactly this build is the tag's source archive below.
Known issues in this pre-release. SHA256SUMS lists the two .deb files with ~ where the download has . (eyrie-desktop_0.1.0~rc.1_amd64.deb is downloaded as eyrie-desktop_0.1.0.rc.1_amd64.deb): rename the file back before checking, or compare its hash by hand. The .rpm's version sorts above later versions, so moving from it to a later one needs sudo rpm -Uvh --oldpackage <file>.rpm. Both are fixed in the next pre-release.