LiteGateIN DEVELOPMENTUSE CASES
Codex, Claude Code, fallback, budgets, chat and LAN: six ways to bring LiteGate into your workflow.
Product scenarios · Public release pending. Client compatibility depends on protocol, version and enabled capabilities.
Connect Codex to one stable endpoint and manage destinations and policies through LiteGate.
Explain a module and generate a test using an explicitly selected model.
Responses, streaming and tool-call compatibility verified against the client version.
Work in your repositories with centralized provider credentials and shared policies.
Review a code change with requests flowing through an Anthropic-compatible gateway.
Messages, streaming and tool support. API access is independent of chat subscriptions.
When a recoverable failure or provider limit occurs, try another allowed destination before delivering the response.
The primary provider returns a rate limit; LG tries the next eligible destination in the ordered list.
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.
Set budgets per tool, project or key, with visible usage, alerts and explicit policies when a limit is reached.
Assign a daily token budget to Codex and Claude Code and block new requests when it runs out.
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.
Talk to your models inside LiteGate, with local history and visible routing decisions.
Edit a message, create a branch and compare responses while preserving portable context.
Implementation integrated; public distribution pending. Portable context excludes private reasoning and provider-internal caches.
Share access with trusted devices through LAN, TLS and keys with scoped permissions and limits.
Use models connected to your LiteGate workstation from a laptop.
Explicit opt-in, TLS and revocable keys. Administration stays local. Local means local to the LiteGate host, not every server on the network.
These scenarios describe product workflows, not verified setup instructions for a public release. 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.