@rectify-so/bridge
v0.1.3
Published
Rectify AgentPulse local bridge — securely connects locally-installed agent CLIs (Claude Code, Codex) and OpenClaw gateways to the Rectify dashboard over a reverse SSH tunnel.
Readme
@rectify-so/bridge
Connect your locally-installed agent CLIs — Claude Code, Codex, and OpenClaw — to the Rectify AgentPulse dashboard.
The bridge runs on your machine, reads your local session data, and opens a secure outbound tunnel so the dashboard can show your sessions, token usage, and let you chat. Nothing is installed system-wide and the bridge only makes outbound connections — no inbound SSH server required.
Usage
In the Rectify dashboard, add a Claude Code / Codex / OpenClaw connection. You'll be given a one-line command:
npx @rectify-so/bridge connect <token>Run it on the machine where the CLI is installed and keep the window open. The dashboard updates automatically once connected. Press Ctrl+C to disconnect.
Options
npx @rectify-so/bridge connect <token> [--api <url>]
--api <url> Override the Rectify API base URL (default: https://api.rectify.so)
-h, --help Show helpRequirements
- Node.js 18+ (already present if you have the Claude Code or Codex CLI).
- The OpenSSH client (
ssh) — built into macOS, Linux, and Windows 10+. - For Claude Code connections: the
claudeCLI on yourPATH. - For Codex connections: the
codexCLI on yourPATH.
What it reads
- Claude Code:
~/.claude/projects/**/*.jsonl(sessions) and~/.claude/skills(skills). - Codex:
~/.codex/sessions/**/*.jsonl(sessions).
Session files are read-only. Chat requests spawn the local CLI (claude --print / codex exec).
How it works
- Fetches its config (tunnel host/port, one-time key) from the Rectify API using the token.
- For Claude/Codex: starts a local HTTP server that serves parsed session data and proxies chat to the CLI.
- Opens a reverse SSH tunnel (outbound) so the Rectify backend can reach that local server. For OpenClaw it simply forwards the gateway port.
License
MIT
