DOCS · LOCAL BRIDGE

The exchange, from your own terminal

Local Bridge is a small CLI. Buyers use it to point an agent client at the exchange for a single session without editing a shell profile. Sellers use it to report their own usage, so their seat is sized from measurement rather than from a guess.

Node 20+Optional — the API works without it

Install and sign in

npm install -g @shaidle/bridge
shaidle login --token sk-shaidle-…

The token is minted in the app under Connect editor. login verifies it against the endpoint before saving, so a typo fails immediately instead of failing later at the first request. shaidle whoami shows which account a saved token belongs to, and shaidle logout forgets it.

Buyer commands

shaidle code [claude args…]: Opens your Claude Code wired to the exchange for that session only. The environment change lives on the child process, so nothing about your normal setup changes and it reverts the moment you exit.
shaidle run "<prompt>" [--provider auto|claude|codex]: Runs a task on the exchange and streams the result. auto lets the exchange pick the best available seat and fail over — including across providers — if one runs out mid-task.
shaidle env: Prints the two environment exports that point a wire-compatible client at the exchange, in both shell dialects. Use this when you want the wiring to be permanent, or to feed something the CLI does not launch itself.

Seller commands

shaidle usage sync [--node <id>] [--watch <min>]: Reports your own usage of the account you connected, so the exchange knows how much of the seat is genuinely spare. Seats that report are sized from measurement and earn more than seats that are estimated. --watch keeps it running on an interval.
shaidle usage show: Prints exactly what sync would send and sends nothing. Run this first if you want to see the payload before trusting it.

Why report at all

A seat whose real consumption is unknown has to be sized conservatively, which means less of it is offered and less of it earns.
Percentage-based headroom read from a provider is biased downward by your own work — reporting is what corrects it.
Your own work always takes priority. Reporting is how the exchange knows to get out of your way before you notice it did not.

The privacy design behind this, and the reasoning about provider terms it sits inside, are set out in the compliance position.