@windowsed/agenttoolbox
v0.1.2
Published
Point Claude Code, Codex, Grok, OpenCode, Continue, Aider, and Zed at a Windowsed AI Gateway. Linux, macOS, and Windows.
Readme
@windowsed/agenttoolbox
Point the coding agents on this computer at a Windowsed AI Gateway.
npx -y @windowsed/agenttoolboxThe prompt asks what to do first: install agents, set them up, back up configs, recover the originals, or a dry run. Set up asks where the gateway is, then the API key. Back on the gateway list returns to the action menu. An empty address or an empty API key also goes back. After the key, every installed agent and the shell file are written (~/.bashrc on Linux, ~/.zshrc and ~/.bashrc on macOS, the PowerShell profile on Windows). The original files are copied to .bak-agenttoolbox first. Quit leaves the menu. A finished action returns to the menu.
- Where the gateway is. Pick this machine,
vm.windowsed.me,ai.windowsed.me, or Other address and type your ownhttp(s)URL. - The API key. It is masked, and it is not printed again.
- The configs are written. An agent that is not installed is skipped.
--only claude,codexlimits the set.
It then calls GET /v1/models and writes the models that answer. Image models are left out. gpt-5.4 is the default when the gateway lists it. Grok, OpenCode, Continue, and Zed each gain a row for every model the gateway lists. Codex keeps the model already in its config. Aider and Claude Code keep one default model. Update models reads the address and key already saved in a config and adds any new id, with no questions. It does not keep running in the background.
What it writes
| Agent | Linux | macOS | Windows |
|---|---|---|---|
| Claude Code | ~/.claude/settings.json | same | %USERPROFILE%\.claude\settings.json |
| Codex | ~/.codex/config.toml | same | %USERPROFILE%\.codex\config.toml |
| Grok | ~/.grok/config.toml | same | %USERPROFILE%\.grok\config.toml |
| OpenCode | $XDG_CONFIG_HOME/opencode/opencode.json | ~/.config/opencode/opencode.json | %APPDATA%\opencode\opencode.json |
| Continue | ~/.continue/config.json | same | %USERPROFILE%\.continue\config.json |
| Aider | ~/.aider.conf.yml | same | %USERPROFILE%\.aider.conf.yml |
| Zed | $XDG_CONFIG_HOME/zed/settings.json | ~/Library/Application Support/Zed/settings.json | %APPDATA%\Zed\settings.json |
| Shell API key | ~/.bashrc | ~/.zshrc and ~/.bashrc | PowerShell profile |
Claude Code's base URL is the bare origin. OpenAI-compatible agents get {origin}/v1. Codex uses the Responses API. Its config.toml names OPENAI_API_KEY with env_key; the key itself goes in the shell file. Choosing Codex during interactive setup writes that shell file too.
The shell block is how a new terminal learns the key. On Linux, bash reads ~/.bashrc for an interactive shell, so the key is written there. Open a new terminal after the command finishes. The first write of each file is copied to *.bak-agenttoolbox.
Zed still wants the API key in its own assistant settings. The URL and the model list are written for you.
Install
Download an agent that is not on this computer yet. Each one uses that project's own installer. Linux and macOS use the shell script. Windows uses the PowerShell script, npm, or winget.
npx -y @windowsed/agenttoolbox install
npx -y @windowsed/agenttoolbox install --only claude,codex
npx -y @windowsed/agenttoolbox install --dry-runBackup
Copy every existing config, including ~/.bashrc on Linux, to a .bak-agenttoolbox file beside it. The live file is not changed. A backup that is already there is left as the first copy.
npx -y @windowsed/agenttoolbox backup
npx -y @windowsed/agenttoolbox backup --dry-run
npx -y @windowsed/agenttoolbox backup --only claudeRecover
Put each .bak-agenttoolbox copy back over the live config. The backup file stays, so you can recover again. A config with no backup is left alone.
npx -y @windowsed/agenttoolbox recover
npx -y @windowsed/agenttoolbox recover --dry-run
npx -y @windowsed/agenttoolbox recover --only claudeWithout the prompt
npx -y @windowsed/agenttoolbox --base http://127.0.0.1:1234 --key "$PROXY_API_KEY"
npx -y @windowsed/agenttoolbox --base http://127.0.0.1:1234 --key "$PROXY_API_KEY" --dry-run
npx -y @windowsed/agenttoolbox --base http://127.0.0.1:1234 --key "$PROXY_API_KEY" --create
npx -y @windowsed/agenttoolbox --base http://127.0.0.1:1234 --key "$PROXY_API_KEY" --only claude,codexPublish
The TypeScript stays in this repo. npm publish runs the build first and uploads a minified bundle, not the sources.
bun install
bun run check
npm publish