Skip to main content
Agent Connect (wirebox connect) connects autonomous AI coding agents running on your local machine (such as Claude Code, Hermes Agent, OpenAI Codex, or OpenCode) directly to real-world communication channels — including Apple iMessage, SMS, and email inboxes. With Agent Connect, you can message your development agent while away from your desk, ask it to review code, run test suites, check deployment status, or fix bugs, and receive interactive approval prompts on your phone before sensitive commands execute.

Architecture & How It Works

Agent Connect establishes a secure, outbound-only WebSocket duplex tunnel between your local environment and the Wirebox Edge routing layer. Incoming webhook events from iMessage, SMS, and email are decrypted, parsed, and dispatched into the appropriate local agent harness.

Quickstart

1. Zero-Setup Execution (npx)

You can launch Agent Connect immediately without installing any permanent global packages:
Or using globally installed wirebox:

2. Test from Your iPhone

  1. Open Messages on your iPhone or Mac.
  2. Text connect @<agent_handle> (for example, connect @eva) to the Wirebox router line:
  3. Once paired, send any instruction (e.g. “Run git status and summarize pending changes”).
  4. Watch your local agent process the task and text the answer back to your phone.
You can also generate an instant QR code to scan with your iPhone camera by running wirebox imessage router <agent_handle>.

Supported Agent Drivers

Wirebox Connect features native drivers for major autonomous coding agent CLIs. It automatically detects which agents are installed on your system:

Checking Driver Availability

To see which drivers are detected and available on your system, run:
Example output:

Human-in-the-Loop Remote Approvals (HITL)

When you are away from your desk, safety is critical. An agent should not run destructive shell commands without human oversight. Agent Connect includes a built-in Escalation Manager. Whenever an agent attempts to perform a sensitive action (such as executing bash scripts, pushing code, or triggering deployments), the local process is suspended, and an approval prompt is pushed directly to your phone:

Responding to Prompts:

  • Text 1 (or yes, allow): Approves the pending action once and resumes execution.
  • Text 2 (or always): Permanently whitelists this tool for the remainder of the current session.
  • Text 3 (or no, deny): Cancels the command. The agent receives an execution rejection notice and adjusts its strategy.

Environment Diagnostics & Setup

Diagnostic Doctor

Run connectivity, credential, and runtime checks before starting:
Output:

Interactive Setup Wizard

If configuring for the first time, run the interactive wizard:
The wizard prompts for your API key, lets you select from available agent handles, detects installed agent harnesses, chooses your default workspace directory, and optionally registers the daemon as a system background service.

Live Scenario Simulation (demo)

Test the entire phone communication and approval escalation pipeline locally without needing a physical phone:

Background Daemon Management (macOS launchd)

You can run Agent Connect as an always-on background service on your Mac so your agents are accessible even when your terminal window is closed:
Background daemon configuration files are placed in ~/Library/LaunchAgents/sh.wirebox.connect.plist. Logs are streamed to ~/.wirebox/connect.log.

Security & Architecture

Agent Connect is designed with enterprise-grade isolation and zero-trust principles:
  1. Outbound-Only WebSocket: The connection is initiated from your machine outward (wss://api.wirebox.sh). Your machine never binds or opens inbound listening ports on 0.0.0.0, ensuring total invisibility to local network (LAN) scanners.
  2. HMAC-SHA256 Cryptographic Verification: Inbound webhook events are verified with agent-scoped secrets (whsec_...). Spoofed or replayed HTTP requests are discarded before reaching the agent.
  3. Contact Allowlist: Only paired contacts (such as your verified supervisor phone number or email) can invoke the agent. Unknown callers are ignored.
  4. Emergency Cut-off: If you ever need to sever an agent’s connectivity instantly, you can disable the tunnel from the Wirebox Console or via CLI: