Download

Get yAGna 0.9.0

yAGna ships as a small portable archive: the binary, a short install note and the license text. No installer wizard, no registry entries, no background service — unpack it and run yagna.exe. Everything yAGna stores lives under one folder in your user profile (%APPDATA%\yagna\) and deleting that folder uninstalls the library completely.

Download the Windows archive (11.5 MB) — yAGna 0.9.0 for Windows 10/11, 64-bit.

The Linux and macOS archives are built by the same release pipeline from the same source — the project's build and test suite runs on all three platforms on every change — but those desktops have not yet had their full manual passes. They appear on this page as soon as the release lands.

From the archive to the library

1. Unpack the archive — in PowerShell: tar -xzf yagna-0.9.0-x86_64-pc-windows-msvc.tar.gz.

2. Put yagna.exe somewhere on PATH, or run it from where you unpacked it.

3. Run yagna doctor once — it reports the token it found (env GITHUB_TOKEN or gh auth token), the API's reachability and rate limit, the data directory and the schema version. It reports, never repairs.

4. Run yagna sync — the first sweep of your stars. The honest pace: about five minutes per thousand repositories, once. After that, everything reads from your disk.

5. Run yagna — the app opens on your library: the list, the topics, the READMEs with their images, the health index on every row.

Two lines in any MCP host

yAGna's Model Context Protocol server ships in the same binary, and the npm launcher yagna-mcp installs it for your host: run npx -y yagna-mcp once to fetch the release, then point your host at it — a server named yagna with the command npx and the argument list -y yagna-mcp:

{ "mcpServers": { "yagna": { "command": "npx", "args": ["-y", "yagna-mcp"] } } }

Already have the binary on PATH? The launcher finds it there, or take YAGNA_BIN to name it directly. The server speaks MCP over stdio and shares the catalog with the app.

What the agent gets

Nine free reads — the deep-search grammar, whole repository records, stored READMEs, your tags and topics vocabulary, the local worktrees, the fit spec — and six writes that stay yours: tags, notes, the fit spec (validated and backed up), a re-score, a refresh, a sweep. The live GitHub tools pass a spend ledger with per-hour and per-minute ceilings from agent.toml, and past the confirmation threshold the server asks your host before spending — a host that cannot be asked gets a refusal, never a silent yes. Every call lands in the activity trace, and the app's title bar says an agent is connected.

yAGna never acts on GitHub for you — no issues, no comments, no pushes. It is the memory, not a second client.

The fine print

yAGna has no telemetry, no accounts and no network calls of its own — the network side is your token talking to GitHub through the forge, and the token is never logged and never leaves the machine. The MCP server reads and writes the same local catalog the app does. Building from source is equally plain: it is Rust and Cargo, and the license is open source with ethical restrictions.

GitLab support is coming — the forge is a trait with GitHub as its first tenant, and GitLab is the next one on the roadmap.