CLI tools
The dashboard can point supported coding CLIs at the proxy for you. Before the first write the original config file is copied into a backup directory and its original values are recorded, so disabling restores exactly what was there — ShareQuota never overwrites its own backup.
| Tool | Config file | What changes |
|---|---|---|
| Claude Code | ~/.claude/settings.json | env entries for the base URL and key |
| Codex | ~/.codex/config.toml | a ShareQuota model_provider section |
| Gemini CLI | environment | base URL pointed at the local endpoint |
The reversibility guarantee
Pointing a CLI at the proxy is a loan, not a takeover. The rule the integration code is written around: never destroy user configuration. In practice that means:
- 1Backup before the first writeThe original config file is copied into the backups directory inside your data dir before anything touches it. The copy is never overwritten by a later enable.
- 2Additive changes onlyEnabling adds the proxy entries; it does not rewrite the rest of your file. Your keybindings, your model preferences, your other providers stay exactly as they were.
- 3Disable restores the original valuesTurning the integration off puts back what was recorded at backup time — not a guess at it. The diff after enable-then-disable is empty.
- 4The backups are yours to inspectPlain files in ~/.sharequota/backups, listed in the dashboard. If you stop trusting the binary, the escape hatch is a copy command you can run yourself.