@strideops/bridge

The Stride Bridge daemon lets StrideOps "Build" agents run on your local machine. Agents dispatched from the StrideOps cloud are executed locally via Claude Code CLI, giving them access to your filesystem, local tools, and private network resources.

Requirements

• Node.js >= 20
• Claude Code CLI installed and authenticated (claude on PATH)

Installation

npm install -g @strideops/bridge
# or
npx @strideops/bridge connect <CODE>

Quick Start

1. Connect to your StrideOps workspace

Get a pairing code from StrideOps > Build > Bridges > New Bridge, then run:

stride-bridge connect <PAIRING_CODE>

This saves credentials to ~/.stride-bridge/config.json and registers your machine.

2. Start the daemon

stride-bridge start

The daemon polls for work items dispatched to your bridge and executes them locally using Claude Code CLI. Press Ctrl+C to stop gracefully.

3. Check status

stride-bridge status

Prints the current configuration, last known state, and whether the StrideOps server is reachable.

4. Run diagnostics

stride-bridge doctor

Checks all prerequisites:

• Node.js version (must be >= 20)
• Claude CLI on PATH and authenticated
• Config file valid and present
• StrideOps server reachable
• Local workspace directory writable

Commands

| Command | Description | |---------|-------------| | stride-bridge connect <CODE> [--api-url <url>] | Pair this machine with StrideOps using a pairing code | | stride-bridge start | Start the daemon (foreground; use a process manager for background) | | stride-bridge status | Print config and connectivity status | | stride-bridge doctor | Run prerequisite checks |

Options

• --api-url <url> — Override the StrideOps API base URL (default: https://app.strideops.ai)

Configuration

Config is stored at ~/.stride-bridge/config.json (chmod 600 on POSIX). It is written atomically to prevent corruption. Do not edit it by hand; use stride-bridge connect to re-pair.

Running as a Background Service

For persistent operation, use your OS process manager:

macOS (launchd) — create a plist in ~/Library/LaunchAgents/.

Linux (systemd) — create a user service unit.

Windows (Task Scheduler) — create a task that runs stride-bridge start on login.

Security

• The bridge token is stored locally and never logged.
• Hook callbacks to StrideOps are signed with a per-agent HMAC secret (SHA-256).
• All HTTP requests use a 10-second timeout.
• Hook scripts are fail-open: if StrideOps is unreachable, the agent continues running.

Uninstalling

npm uninstall -g @strideops/bridge
rm -rf ~/.stride-bridge