Run Agentrails yourself.
Install the CLI from npm for terminal and background-service workflows, or run the desktop app from source for visual review and guided setup. Both use the same local archive and provider state. Automatic cloud backup and clean-device restore are not enabled in v0.1.
Choose
Desktop and CLI open the same archive.
You can switch between them on one machine. Do not run two long-lived background services against the same data directory.
Interactive setup and archive review
Approval dialogs, manual hook instructions, thread detail, storage connection setup, and sync status
Headless machines, scripts, and terminal workflows
JSON output, a per-user background service, filtered search, and explicit export paths
CLI
Install the command line app.
Use the CLI on a workstation or headless machine. It can initialize the archive, connect providers, run the background service, and search captured history.
npm install --global @agentrails/cli
agentrails init
agentrails providers listDesktop
Run the desktop app from source.
You need Node.js 22.13 or newer and pnpm 11. The development command starts the desktop app with provider setup, archive search, exports, and integrity checks.
git clone https://github.com/skyaara/agentrails.git
cd agentrails
pnpm install --frozen-lockfile
pnpm desktopOpen the repository Build an installer
Platform packaging is configured in the repository. Prepare the pinned rclone binary, then build the desktop installer for your current platform.
pnpm package:desktopFirst run
Connect one source, then confirm the archive.
- Open the provider catalog and choose a surface with an approved hook, documented local history, or supported import.
- Approve automatic hook setup, follow the manual instructions, or select an export file. Agentrails does not scan arbitrary folders.
- Finish an agent run, then use
agentrails syncor the desktop Sync action to process it. - Inspect the thread's coverage label and run
agentrails verifybefore relying on the archive.
Before capture
Read what Agentrails can access.
Provider connections are explicit. The product never uses browser cookies, account sessions, or private web endpoints.
