Getting started

Use Synaxi in one command.

Synaxi runs locally for the life of your coding session. It keeps your provider connection, applies request optimizations on your machine, and disappears when the tool exits.

Install

On macOS, install the stable CLI from the Synaxi Homebrew tap:

brew tap BeadW/synaxi
brew trust BeadW/synaxi
brew install synaxi

To update an existing installation:

brew update
brew upgrade synaxi

Run a tool

Use the wrapper that matches your coding tool. The runtime is started for that session only.

Claude Code

Uses Claude Code’s native Anthropic routing.

synaxi wrap claude

Codex

Uses Codex’s Responses-compatible routing without changing your global config.

synaxi wrap codex

Pass normal tool arguments after the wrapper command, for example synaxi wrap claude --dangerously-skip-permissions.

Account and dashboard

Sign in once when prompted. The same account works at dashboard.synaxi.ai, where you can see your own usage, token consumption, and optimization activity.

Authentication persists across sessions. To run locally without linking telemetry, use the explicit opt-out:

synaxi wrap claude --anon
synaxi wrap codex --anon

Local by default

  • Prompts, responses, and source code stay between your machine and your model provider.
  • Synaxi sends metadata-only usage events when you are signed in.
  • No certificate, system proxy, tray app, or resident Synaxi daemon is required.
  • Optimization tables remain local so rewritten identifiers can be restored safely.

Troubleshooting

Connection refused

Start a fresh wrapped session. Synaxi owns one local runtime per invocation; do not reuse an old provider URL from a previous session.

The command is not found

Install the underlying tool first, then run its Synaxi wrapper. For example, install Claude Code or Codex and confirm claude --version or codex --version works before wrapping it.

See whether traffic arrived

While a runtime is running, its local health endpoint reports received Claude requests at /health/requests. The dashboard updates when usage telemetry is recorded.