USE CASES
Your workflow.
More control.
Codex, Claude Code, fallback and token budgets: four ways to bring LiteGate into your workflow.
Planned capabilities · Integrations and policies are not yet verified in LiteGate.
01 / PLANNEDCodex, on your terms
Connect Codex to one stable endpoint and manage destinations and policies through LiteGate.
Example scenario
Explain a module and generate a test using an explicitly selected model.
Requirements and boundaries
Responses, streaming and tool-call compatibility verified against the client version.
02 / PLANNEDClaude Code, connected
Work in your repositories with centralized provider credentials and shared policies.
Example scenario
Review a code change with requests flowing through an Anthropic-compatible gateway.
Requirements and boundaries
Messages, streaming and tool support. API access is independent of chat subscriptions.
03 / PLANNEDA backup plan for your models
When a recoverable failure or provider limit occurs, try another allowed destination before delivering the response.
Example scenario
The primary provider returns a rate limit; LG tries the next eligible destination in the ordered list.
Requirements and boundaries
Fallback is only allowed before the first visible output. After that point, errors are reported without silently restarting. Local mode never allows a cloud destination.
04 / PLANNEDYour tokens, your budget
Set budgets per tool, project or key, with visible usage, alerts and explicit policies when a limit is reached.
Example scenario
Assign a daily token budget to Codex and Claude Code and block new requests when it runs out.
Requirements and boundaries
Tokens and money are accounted for separately. Hard limits require capacity reservations for concurrent requests and reconciliation with actual usage. An alternative model is only allowed if it meets policy and enough budget remains.
These scenarios describe the planned product, not working setup instructions. Each guide will include prerequisites, configuration, a reproducible check and tested client versions. LG policies cover traffic routed through LG, not all client network activity.