Subcommands
| Command | What it does |
|---|
reclaude | Start the daemon and run Claude Code (the everyday command) |
reclaude app | Launch Claude Desktop with your codewing-assigned account (Dedicated plan, closed beta); on first run / startup it automatically downloads and updates the required Claude Desktop (macOS / Windows only) |
reclaude app-reset | Reset Claude Desktop login state (clear cookies / cache; does not affect reclaude itself) |
reclaude app-update | Check and update the local Claude Desktop; add --check to only check without downloading |
reclaude login | Browser device-flow login, bind this machine |
reclaude logout | Restore the Claude Code config from before the last login |
reclaude org | View or switch the organization for this device |
reclaude config gateway | View, lock, or reset the gateway used for connections |
reclaude status | Print daemon status and the path to claude |
reclaude stop | Stop and disable the background daemon |
reclaude update | Check and upgrade reclaude (--check only checks) |
reclaude setup | Copy reclaude to the standard location and add it to PATH (use after a manual download) |
reclaude unsetup | Undo what reclaude setup wrote to the standard location and PATH |
reclaude uninstall | Stop the daemon and wipe all local state |
reclaude version | Print the current version |
reclaude logs | Print the tail of the daemon log |
reclaude help | Print help text |
Plain reclaude with no subcommand = start the daemon and open Claude Code. That’s the everyday use.
Common flows
First-time setup:
reclaude login # browser-authorize once
reclaude # start daemon + open Claude Code
Pause service:
reclaude stop # stops the daemon; running reclaude again starts it
Upgrade:
Full uninstall:
Switch organization
reclaude org list # list all orgs and the device's current binding
reclaude org use <org_id> # switch this device to the given org
The next request will use an account from the new org.
Logs
The log file lives at ~/.reclaude/logs/daemon.log. Use reclaude logs to print the tail.
The gateway is reclaude’s entry point to the service. By default the daemon probes a list of candidates at startup and picks the fastest (auto mode); pin a specific URL if you want to lock onto one (manual mode).
| Subcommand | What it does |
|---|
reclaude config gateway | Probe all candidates interactively and save your pick as the manual choice |
reclaude config gateway test [url] | Probe only, don’t save. With a url tests one; without, tests all |
reclaude config gateway set [--force] <url> | Set directly. Probes first; --force skips the probe |
reclaude config gateway current | Print the gateway in effect and its source |
reclaude config gateway reset | Clear the manual override and return to auto |
Pick the fastest interactively:
Each candidate’s reachability and latency is printed live. Press Enter for the fastest, type a number to pick a specific one, or q to cancel.
See what’s in effect:
reclaude config gateway current
Prints url (the URL actually in use), source (RECLAUDE_GATEWAY_URL / device.json / default), and mode (manual or auto).
Reset to auto:
reclaude config gateway reset
If the daemon is running when you save, run reclaude stop && reclaude to apply.The RECLAUDE_GATEWAY_URL environment variable wins over any local config.