One shared local endpoint
Point supported agents at one stable localhost gateway instead of teaching every tool a different provider-specific config.
One localhost endpoint for supported agents
Modmux lets Claude Code, Cline, and Codex share the same local GitHub Copilot gateway so you stop redoing provider setup for each tool.
Open source, localhost-only, and reversible by design.
$ modmux start
Starts a local gateway and completes GitHub auth
$ modmux configure claude-code
Points your agent at the shared localhost endpoint
$ modmux status
Shows endpoint, auth, and usage state in one place
Why use Modmux
Modmux centralizes the messy part of agent setup: provider wiring, local endpoints, usage visibility, and cleanup when you want to back out.
Point supported agents at one stable localhost gateway instead of teaching every tool a different provider-specific config.
Modmux binds to 127.0.0.1. Supported config changes
can be undone with modmux unconfigure when you want
to restore the original setup.
Check status, health, models, and Copilot quota usage without guessing what is running behind the scenes.
How it works
A supported agent talks to Modmux on localhost. Modmux translates compatible request and response shapes, then forwards them through GitHub Copilot.
Claude Code, Cline, or Codex sends requests to one local endpoint instead of maintaining separate provider wiring.
Exposes compatible endpoints, translates traffic, and keeps auth, status, and usage visible from the CLI.
/v1/messages/v1/chat/completions/v1/responses/v1/models, /v1/usage, /health
Modmux authenticates with GitHub and forwards requests through the Copilot-backed model path with a local-first trust boundary.
Proof
Modmux is easiest to understand from the terminal: start the local gateway, configure an agent, and inspect the live endpoint and usage state.
modmux start
Completes GitHub auth, starts the localhost service, and enables real Copilot usage visibility by default.
modmux configure claude-code
Writes reversible local config so Claude Code uses the shared endpoint instead of a separate provider setup.
modmux status
curl http://127.0.0.1:11435/v1/usage
Confirms the active endpoint, auth state, and Copilot quota data from the same local runtime.
Install
The fastest path is still from source. If you do not want the Deno runtime on your machine, use a direct binary from GitHub Releases.
Clone the repository and install globally with the current Deno task. This is the easiest way to stay current while the project is moving quickly.
git clone https://github.com/modmux/modmux.git
cd modmux
deno task install
modmux start and complete GitHub auth.modmux configure claude-code.modmux
status.
Download a platform build from GitHub Releases if you want to skip the runtime dependency and get straight to setup.
FAQ
You can, but every tool tends to drift into its own config path, provider format, and recovery workflow. Modmux keeps that setup centralized so switching agents does not mean starting over.
Yes. Modmux routes requests through GitHub Copilot, so you need an active Copilot-backed account.
No. The service binds to 127.0.0.1, so it stays
local to your machine.
Yes. Supported agent configuration is reversible by design with
modmux unconfigure.
The built-in registry currently includes Claude Code, Cline, and Codex.
Yes. By default, Modmux manages the Copilot CLI sidecar needed
for real quota visibility through /v1/usage. Run
modmux set copilot off if you want to disable it.
Deno is only required for the recommended source install. Downloading a direct binary from GitHub Releases does not require it.