Arivu
Documentation menu
Reference

Command Line Interface

Use the Arivu binary to run the server, log in, capture, list, search, and migrate legacy exports with audience-scoped authentication.

The same Go binary serves the app and provides CLI commands. CLI sessions use their own bearer-token audience and cannot be reused as browser or extension sessions.

Build and Run

git clone https://github.com/glnarayanan/arivu.git
cd arivu
go build -trimpath -ldflags="-s -w" -o arivu ./cmd/arivu
./arivu version
./arivu serve -addr 127.0.0.1:8080 -db arivu.sqlite3

Open http://127.0.0.1:8080/auth and create an account before CLI login.

Log In

./arivu login \
  --api http://127.0.0.1:8080/api \
  --email you@example.com \
  --password your-password

The CLI stores its API URL and tokens in the local user configuration directory. ARIVU_API supplies a default URL when --api is omitted.

Capture and Retrieve

./arivu save https://example.com/article
./arivu list
./arivu search "vector databases"

CLI capture uses the same owned bookmark pipeline and server-side URL safety checks as the browser app.

Local Automation

CLI-audience tokens can call /api/agent/* routes for scoped Search, Library, Graph, Insights, feedback, saved bookmark and note reads, note creation, tasks, reminders, decisions, collections, feed subscriptions, and public-share management. These are API capabilities for local tools, not additional top-level arivu commands and not a hosted automation platform.

See API Reference for the route overview.

Legacy Migration

./arivu migrate --json-export legacy-export.json --dry-run=true

Apply only after reviewing the dry run:

./arivu migrate \
  --json-export legacy-export.json \
  --sqlite-db arivu.sqlite3 \
  --old-secret-key "$OLD_SECRET_KEY" \
  --new-secret-key "$SECRET_KEY" \
  --dry-run=false

Production Installer

arivu-installer is a separate command for Linux VPS plan, install, status, backup, restore, upgrade, reconfigure, and uninstall workflows. It does not require gh. See Self-Hosting Arivu.

Avoid passing long-lived secrets in shared shell history. Treat local CLI tokens as access to your private knowledge store.