Skip to main content

Command line

Augmunt智能路由8/21/26About 2 min

Log in (once per device)

clauded login

The terminal prints an authorization link and opens your browser. Sign in to the console and click Approve; the terminal then shows:

Device #1042 registered ✓  (~/.clauded/device.json)

One subscription works on several computers. Each device logs in once, and the console lists which devices are active so you can revoke any of them at any time.

clauded logout clears the registration and restores your original Claude credentials.

Check status

clauded status
claude:  ~/.clauded/claude-cli/2.1.220/claude (managed by clauded) · 2.1.220
device:  #1042
gateway: https://api.augmunt.com
email:   you@example.com
         (reachable, 112ms)
daemon:  running (pid 34127) at http://127.0.0.1:53219

This is the first screen to look at when something is wrong: is the device registered, is the route reachable, is the background service running, has an account been assigned. If the answer is not here, see Troubleshooting.

Four ways to use it

Surface Command Notes
Command line clauded Launches Claude Code through the proxy; the background service and Claude Code itself are prepared automatically
Web clauded web Opens the official chat UI in your browser on the same account. Needs no background service — the lowest-friction entry
Desktop clauded app Downloads, installs and launches the Claude desktop app through the proxy (macOS)
Editors clauded ide install Points the official Claude extension in VS Code / Cursor / Windsurf at clauded — restart the editor to take effect

Anything you pass after clauded is forwarded verbatim to Claude Code, so your usual habits keep working:

clauded                        # interactive session
clauded "split this function"  # start with a prompt
clauded --resume               # Claude Code's own flags work as usual

Desktop app complains about an untrusted certificate

The component embedded in the desktop app only trusts the system certificate store. Run clauded cert install once (it will ask for administrator approval).

Codex runs through codexd

The same install also provides the codexd entry point. Its command tree is identical to clauded — it just launches Codex instead:

codexd                # CodeX CLI
codexd web            # ChatGPT web version
codexd app            # CodeX desktop app
codexd ide install    # the Codex extension in your editor

Claude and Codex are two independent subscriptions, each with its own account and runtime.

The background service

You normally never touch it — running clauded starts it for you. When you do need to:

clauded daemon    # run the forward proxy in the foreground
clauded stop      # stop it
clauded install   # register it to start at boot

Which Claude Code to run

A machine can easily hold several copies of Claude Code (the official installer's, a global npm / bun install, and the one clauded downloads). The first line of clauded status names the one in use and its version. You choose the preference:

Preference Behaviour
managed (default) Only the copy clauded manages; downloads it on first launch if missing
system Only the copy installed on your PATH; errors out if absent and never downloads
auto Prefers the system copy, falls back to the managed one
clauded config claude current                      # which one is in use
clauded config claude source managed               # switch preference
clauded config claude path /usr/local/bin/claude   # pin one executable
clauded config claude reset                        # back to defaults

Pinning a path overrides the preference entirely; click back to source managed or source system to return to automatic selection. The Codex side mirrors this: clauded config codex ….

Switch routes

clauded config gateway pick      # list candidates with latency, pick one
clauded config gateway test      # test the current route
clauded config gateway current   # show the current route
clauded config gateway reset     # back to automatic selection

Logs

clauded log on       # per-request logging (full request / response bodies)
clauded log status
clauded log off

Logs are written to ~/.clauded/logs/daemon.log. Off by default — remember to turn it back off once you are done debugging.

A few commands are not expanded on this page; see the command reference, or run clauded help any time.

Last Updated