SynOI

Product · SynOI Connect

Testing

Point this machine at your gateway.
One command, zero dependencies.

@synoi/connect is the on-ramp for connecting your own infrastructure: the hosted gateway is the brain that decides, your workstation is the hands that execute. Run one command and it writes the env vars Claude Code, Cursor, Aider, and OpenClaw already read, confirms the target is actually a SynOI gateway before touching anything, and persists the setting across reboots. It is routing only, on purpose: your provider keys and your license stay in your own environment, never in a SynOI database.

Install instructionsPricing

Split trust

The gateway decides. Your machine executes. Neither one holds the other's secrets.

This is how paying customers connect their own services to SynOI: the gateway you already run (self-hosted or hosted) is the brain: it evaluates policy, mints signed receipts, routes HITL approvals. Your workstation is the hands: it still runs Claude Code, Cursor, or whatever you already use, with your own provider keys, unchanged.

Connect's job is narrow and honest about it: point local tools at the gateway. It does not hold your keys, does not execute governed actions itself, and does not run a background service. It writes environment variables, checks that the target answers like a real SynOI gateway, and gets out of the way.

Today that is routing only. There is no vault custody, no key escrow, no daemon. What ships is the on-ramp: get every tool on the machine pointed at the same governed gateway with one command instead of hand-editing shell profiles.

What gets written

# Claude Code, Anthropic SDK

ANTHROPIC_BASE_URL=<gateway>/anthropic

# Cursor, Aider, Continue, OpenAI SDK

OPENAI_API_BASE=<gateway>/v1

# SynOI desktop-helper, OpenClaw guard

SYNOI_GATEWAY_URL=<gateway>

# tenant auth, hosted gateway only

SYNOI_API_KEY=(your license, optional)

Quick start

One line, whichever gateway you are pointing at.

  1. 01

    Same-LAN gateway

    Running the gateway on a Mac (or any box) on the same network? Give Connect the host and it probes /health and /status to confirm it is actually a SynOI gateway before writing anything.

    npx @synoi/connect mac.local:3000

  2. 02

    Hosted SynOI

    Pointing at the hosted gateway instead? Pass the URL and your license key; SYNOI_API_KEY gets set alongside the routing vars.

    npx @synoi/connect --gateway https://gateway.synoi.systems --license synoi-sk-...

  3. 03

    Check what's set

    See exactly which env vars are live on this machine right now, without digging through shell profiles by hand.

    npx @synoi/connect status

What it does today

Narrow, honest scope: routing setup, nothing more.

Confirms it's a real gateway

Probes the target's /health and /status endpoints before writing anything, so a typo'd hostname or an unrelated service doesn't silently get your traffic.

Cross-platform persistence

Windows gets HKCU\\Environment via setx (visible after a terminal restart). macOS and Linux get an append to ~/.zprofile, ~/.bash_profile, or ~/.profile depending on your shell.

Zero dependencies

The published package has no runtime dependencies. It's a small CLI that shells out to the platform's own tools (setx, shell rc files), not a framework.

status shows what's live

npx @synoi/connect status prints the current ANTHROPIC_BASE_URL, OPENAI_API_BASE, SYNOI_GATEWAY_URL, and whether a license key is set, without ever printing the key in full.

--dry-run before you commit

Preview exactly what would be written to your shell profile or the Windows registry before anything actually changes.

LAN discovery (early)

A discover subcommand scans the LAN for SynOI gateways over mDNS. It's early: the interactive picker described on the roadmap isn't built yet, and it needs the optional multicast-dns package installed separately.

Not yet shipped

We'd rather tell you what's coming than pretend it's here.

Interactive discover picker

Pending

Full mDNS browse with a pick-from-list flow. Today discover finds gateways; choosing one and applying it is still manual.

Tool-specific config files

Pending

Auto-writing Claude Code's MCP config or Cursor's settings directly, instead of just the shared env vars, is on the roadmap.

Login-time install hooks

Pending

Running Connect automatically at login (Windows scheduled task, macOS LaunchAgent) is not built yet.

This is how you connect your own infrastructure.

One command on each workstation, and every tool on it routes through your governed gateway. Your keys never move.

Install instructionsPricing