Best fit
- You want AI apps to keep one stable local endpoint.
- You need provider switching, request logs, cost visibility, or failover.
- You want client config changes to be reversible.
Not ideal
- You use one client, one provider, and the setup rarely changes.
- You do not need logs, failover, cost tracking, or config rollback.
The goal
Keep Claude Code's familiar workflow, but move model traffic through a local gateway so the upstream provider can be changed without repeatedly editing client config.
Setup path
Add DeepSeek as a provider, choose the route profile you want, start AgentGate, then apply the Claude Code config from the client page. Use the logs page to confirm the provider and model selected for each request.
When to use it
This is useful when you want cheaper model runs, local request history, or quick fallback between providers while still using Claude Code as the front-end client.