Download Relay for Windows.
Download the offline desktop Library. The public repository and CLI remain available for contributors and advanced workflows. No credentials, tokens, or private workspaces on this page.
Install the desktop app first.
Current desktop candidate: 0.1.16 · last published: 0.1.5 · Relay protocol: 0.1.0 · internal unsigned preview
-
Windows installer
Download Project Relay Library Setup from the public GitHub Release, choose an install folder, and optionally create a desktop shortcut.
-
Portable option
Use Project Relay Library Portable when you want to run Relay without installing it. The local archive starts blank.
-
First launch
Choose Find my AI conversations. Relay scans metadata first, shows a preview, and waits for your confirmation before copying anything.
-
Round-table review
Open the desktop Review tab, ask a bounded question, select local workers, and inspect their replies and comparison packet before recording any human decision.
-
Clone the public repository
Use the public GitHub repository when you want to inspect the source, run tests, develop the CLI, or build the desktop app yourself. It is not required for ordinary use.
git clone https://github.com/brendohxd/Project-Relay.gitThen run
cd Project-Relay,npm install, andnpm run check.
What you need first.
-
Node.js 24 or newer
Relay targets a current Node LTS line. Confirm with
node -vbefore installing. -
Git and a clean working tree
Start from a fresh clone of github.com/brendohxd/Project-Relay.
Four commands from a clean clone.
-
1 · Clone
git clone https://github.com/brendohxd/Project-Relay.gitThen
cd Project-Relay. -
2 · Install
npm installInstalls workspace packages from the published lockfile.
-
3 · Check
npm run checkValidates the public surface, schemas, examples, and Pages bundle on a clean tree.
-
4 · Local multipage console
npm run consoleServes this site from
apps/console(defaulthttp://127.0.0.1:4173). Directory routes match GitHub Pages:/status/,/architecture/,/download/, and so on.
Wire a client without tokens.
-
Stdio MCP process
The local MCP server uses stdio and reads the workspace in
RELAY_WORKSPACE(current directory by default). No API keys or OAuth tokens appear in this public config.Example client config (paths are placeholders — replace with your absolute paths):
{ "mcpServers": { "project-relay": { "command": "npm", "args": ["--prefix", "/absolute/path/to/Project-Relay", "run", "mcp"], "env": { "RELAY_WORKSPACE": "/absolute/path/to/a/relay-workspace" } } } }Start the process with
npm run mcpfrom the repo root when your client expects a manual launch.Client-specific MCP setup lives under
docs/clients/in the repository. -
Inspect fixtures
Use
examples/m1for the full local remediation loop, orexamples/minimalfor the smallest M0 kernel fixture.
Download quickly, configure deeply later.
- Basic setup
Choose a profile, local workspace name, and whether to start empty or review detected conversations.
- Advanced setup
Configure workspace purpose, local password unlock, archive defaults, Library modules, and read-only connector discovery. Choose General Archive, Scientific / Research, or AI Tooling & Integration Lab for MCP/plugin and runtime debugging work. Advanced setup can be resumed later.
- Optional tutorial
Take the guided tour now, skip it, defer it, or reopen it from Settings. The tutorial uses empty-state examples and never imports files.
- Large archives
Archive now supports bounded pages, model/category filters, select-all-matching, and bulk categorisation. Encrypted AES-256-GCM backups are available locally from Settings; standard local storage is not automatically encrypted.
Public docs on GitHub.
-
Publication boundary
docs/PUBLICATION_BOUNDARY.md - what must never enter a public export or transcript archive.
-
Protocol
docs/PROTOCOL.md — decision gates, evidence, and review rules.