Install · 60 seconds · clean machine

Three commands.
One minute.

Sentinel installs as a global npm package and starts a local runtime on your machine. No cloud account. No telemetry without opt-in. Your API keys stay in ~/.aria/ at mode 0600.

Step 01

Install the CLI

~20 sec
$npm install -g @aria_asi/cli 
added 142 packages in 14.8s
linked binaries:
  aria          → ~/.npm-global/bin/aria
  atlas         → ~/.npm-global/bin/atlas
  atlas-mcp     → ~/.npm-global/bin/atlas-mcp
▸ install ok  @aria_asi/cli@0.4.0 · 46 files · 88,297 bytes
verifyaria --version should print aria 0.4.0.
Step 02

Initialize the local runtime

~25 sec
$aria setup 
▸ creating ~/.aria/ (mode 0700)
▸ writing capability passport           sha256:c4d97e02…
▸ starting connector sidecar     :4319  ready
▸ starting harness daemon        :8790  ready
▸ starting local Qdrant memory   :6333  ready
▸ installing hooks on Claude Code, Codex, OpenCode  3/3
▸ scheduling first Sentinel cycle          queued
▸ setup ok  first cycle in 60s · `aria status` to check
portsconnector sidecar :4319 · harness daemon :8790 · local memory :6333. All localhost-only.
Step 03

Connect your provider keys (BYOK)

~15 sec
$aria connect 
Aria connect  — bring-your-own-key, never leaves this machine

  [ ] Anthropic      ANTHROPIC_API_KEY   detected in env
  [ ] OpenAI         OPENAI_API_KEY      missing — skip?
  [ ] DeepSeek       DEEPSEEK_API_KEY    missing — skip?

▸ writing ~/.aria/keys.json (mode 0600)           ok
▸ verifying anthropic key                       200 OK
▸ binding connector → claude_code / codex / opencode 3/3
▸ connect ok  your code never leaves this machine
privacykeys stored locally at ~/.aria/keys.json mode 0600. Coach events store only hashed previews. No outbound telemetry without explicit opt-in.
What just happened

Six things you now have running, locally.

aria setup wires the connector, harness, kernel, and Sentinel into your three coding agent surfaces. After it returns, Sentinel is already scheduling its first scan cycle against your repo and runtime. Below: what each port is.

  1. 01 · hooks Hooks installed on Claude Code, Codex, OpenCode. Every turn from any surface now routes through the harness gate ladder before it can call a tool. 3 surfaces
  2. 02 · sidecar Connector sidecar started. Local provider proxy + capability passport issuer. Talks to your model API on your behalf using your BYOK key. :4319
  3. 03 · harness Harness daemon started. Per-turn packet injection (cognition, axioms, skills, memory) and substrate-binding enforcement. :8790
  4. 04 · memory Local Qdrant memory started. All embeddings and indexes on-disk on this machine. No cloud dependency for core enforcement. :6333
  5. 05 · passport Capability passport issued and hashed. Default cap max_autonomy_level: 2. Sentinel can propose repairs and emit verifications. It cannot execute on live runtime without explicit allowlist. L2 cap
  6. 06 · cycle First Sentinel cycle scheduled. Watchers warm up over ~60 seconds; the first finding.created event lands in the local ledger. ~60s
BYOK · bring-your-own-key

Your API keys stay in ~/.aria/ at mode 0600. We never see them.

The connector sidecar proxies model calls locally with your key. Coach and gate events store only hashed previews of payloads. No telemetry leaves your machine without an explicit opt-in flag on first run. Your code never leaves your laptop.

Verify

Confirm it's working.

One command tells you whether the runtime is up, the passport is sealed, Sentinel is scanning, and the Atlas substrate is fresh.

terminal · aria status
$ aria status

Aria runtime
  ▸ owner mode                  active
  ▸ capability passport         sha256:c4d97e02… · sealed
  ▸ connector sidecar :4319     healthy
  ▸ harness daemon    :8790     healthy
  ▸ local memory      :6333     healthy

Atlas substrate
  ▸ atlas-server.service        active
  ▸ snapshot                    #186 · sha 09b7b959
  ▸ nodes / edges               35,800 / 39,800
  ▸ codebase-awareness daemon   watching 3 repos

Sentinel daemon
  ▸ atlas-sentinel.service      active
  ▸ last cycle                  2026-05-17 21:30Z · ok=true
  ▸ findings / routed           74 / 5
  ▸ autonomy cap                L2 · propose + verify

All systems sealed and reporting.  → try `aria sentinel ledger` to view findings.

Open your first finding.

Once aria status reports green, the public ledger view mirrors what your local install is producing.

Open the ledger → How it works