The CLI bridge

Concept

The CLI bridge

The bridge is optional. Run aarmos dev in a project folder and it opens a localhost WebSocket on 127.0.0.1:7423, pairing the PWA to that port. A green CLI paired pill appears bottom-left with a Local node connected toast.

Safety posture

  • Workspace-jailed — paths outside the launched folder are refused
  • Origin-checked handshake with a per-session token
  • Dry-run ON by default: file writes and shell commands land in the review drawer with a full diff first
  • Every applied action produces an AVAR receipt

Close the tab or Ctrl+C anytime — the CLI keeps listening (◇ Client disconnected. Standing by…); killing it swaps the pill to local node lost with the reconnect command.

Not the same as observation

The bridge is a development tool for a project folder: it can propose edits and commands, behind review. Watching a running runtime is a different thing — aarmos observe starts a read-only observation service on loopback port 7682, paired with a short-lived code and carrying a single read capability. See observe a local runtime.

Aarmos works standalone without the bridge. See quickstart for the 60-second path.