Amp
Configure Sourcegraph's Amp coding agent to route through aiXbox.app using CLIProxyAPI for unified model access and billing.
Model slugs in examples are illustrative. Confirm current availability in the live catalog and your account's /v1/models before use.
What This Does
Amp is Sourcegraph's frontier coding agent for the terminal and editor. It supports multiple agent modes — smart, rush, and deep — and integrates with IDEs like VS Code, JetBrains, and Zed. By routing Amp through aiXbox.app via CLIProxyAPI, you can use any supported model while consolidating your AI spend under a single aiXbox.app account.
Amp's native BYOK (Isolated Mode) has been removed. To use aiXbox.app with Amp, you need CLIProxyAPI — a lightweight proxy server that intercepts Amp's API calls and routes them through your aiXbox.app endpoint.
Setup
Step 1: Install Amp
curl -fsSL https://ampcode.com/install.sh | bashOr via npm:
npm install -g @anthropic-ai/ampStep 2: Install CLIProxyAPI
CLIProxyAPI is a proxy server that wraps Amp's API calls to route through custom providers:
docker pull eceasy/cliproxyapiOr install from source:
git clone https://github.com/router-for-me/CLIProxyAPI.git
cd CLIProxyAPIStep 3: Configure CLIProxyAPI
Create a config.yaml for CLIProxyAPI:
server:
port: 3456
upstream-url: "https://ampcode.com"
upstream-api-key: "YOUR_AMP_API_KEY"
restrict-management-to-localhost: true
model-mappings:
claude-opus-4-6: "claude-opus-4.8"
claude-sonnet-4-6: "claude-sonnet-4.6"
claude-haiku-4-6: "glm-5.3-flash"
force-model-mappings: true
custom-providers:
- name: "aiXbox.app"
base-url: "https://api.aixbox.online/v1"
api-key: "YOUR_aiXbox.app_API_KEY"
models:
# Frontier flagships
- "gpt-5.6-sol"
- "gpt-5.6-terra"
- "claude-opus-4.8"
- "claude-sonnet-4.6"
# Code-specialized
- "kimi-k2.7-code"
# Other available options
- "kimi-k2.6"
- "deepseek-v4-pro"
- "minimax-m3"
- "glm-5.3-flash"
- "gemma-4"Replace YOUR_AMP_API_KEY with your Amp key from ampcode.com/settings and YOUR_aiXbox.app_API_KEY with your aiXbox.app key from aixbox.online/keys.
Step 4: Start CLIProxyAPI
docker run -d \
--name cliproxyapi \
-p 3456:3456 \
-v ./config.yaml:/CLIProxyAPI/config.yaml \
eceasy/cliproxyapiStep 5: Configure Amp to Use the Proxy
Point Amp to the local proxy by setting environment variables:
export ANTHROPIC_BASE_URL="http://localhost:3456"
export ANTHROPIC_API_KEY="YOUR_aiXbox.app_API_KEY"Add these to your ~/.zshrc or ~/.bashrc to persist across sessions.
Step 6: Verify the Connection
Run Amp and start a conversation:
ampTry a simple prompt to confirm the proxy is routing requests through aiXbox.app.
Recommended Models for Amp
| Amp Mode | Mapped Model | Why |
|---|---|---|
| Smart (frontier reasoning) | claude-opus-4.8 | Anthropic's flagship — best long-context reasoning and code understanding |
| Smart (alternative) | gpt-5.6-sol | OpenAI's GPT-5.6 flagship — strong general reasoning, 1M context |
| Rush (quick tasks) | glm-5.3-flash | Available option for everyday tasks; response times vary |
| Deep (extended thinking) | claude-sonnet-4.6 | Strong code-focused reasoning at lower cost than Opus |
| Large codebase analysis | minimax-m3 | 1M token context, low per-token cost |
| Bulk / cost-optimised | gemma-4 | Lowest-cost active text model in the catalog |
IDE Integrations
Amp also works with IDEs. After configuring CLIProxyAPI, connect Amp to your editor:
| IDE | Setup |
|---|---|
| VS Code / Cursor / Windsurf | Install Amp CLI, ensure editor is running, then run amp |
| JetBrains | Install Amp CLI, then run amp --jetbrains |
| Zed | Install Amp CLI, ensure Zed is running, then run amp |
| Neovim | Install Amp CLI and the Amp Neovim plugin, then run amp |
Use the command palette (Ctrl+O) and select ide connect to link Amp with your editor.
Troubleshooting
Proxy not starting
- Verify Docker is running:
docker ps - Check CLIProxyAPI logs:
docker logs cliproxyapi - Ensure port 3456 is not in use:
lsof -i :3456
Amp connection errors
- Confirm the proxy is running at
http://localhost:3456 - Verify
ANTHROPIC_BASE_URLis set correctly - Test the proxy directly:
curl http://localhost:3456/health
Model mapping not working
- Check that
force-model-mappings: trueis set in your CLIProxyAPI config - Verify the model names in
model-mappingsmatch what Amp requests - Review CLIProxyAPI logs for unmapped model requests
Authentication errors
- Ensure your aiXbox.app API key is valid at aixbox.online/keys
- Check that the
custom-providerssection has the correctapi-key
Notes
- Amp's native Isolated Mode (BYOK) has been removed — CLIProxyAPI is the recommended way to use custom providers
- The
model-mappingssection translates Amp's default model names to aiXbox.app models - All token consumption routed through aiXbox.app appears in your dashboard in real-time
- Amp uses AGENTS.md files for project-specific guidance — these work independently of the proxy setup