Providers
KalCode works with the AI coding tools you already use, on your own accounts. Connecting them is free on every plan.
KalCode is in private development. This page describes the product as it is designed; details may change before release.
Supported providers
The first providers KalCode is being built to connect:
- Claude Code — the local CLI, using your own signed-in session or API key.
- Codex — the local CLI, with its documented approval and sandbox settings.
- Gemini CLI — the local CLI, with its documented non-interactive output modes.
More providers can be added later through a documented adapter contract. Each integration is verified against the provider's current official documentation before it ships.
How connections work
KalCode uses only legitimate, documented integration methods: an authenticated local CLI, documented sign-in flows, API keys you provide, or enterprise credentials. It never scrapes browser credentials, copies hidden session credentials, or reverse-engineers private authentication.
Your usage of each provider is billed by that provider under your account, exactly as it is when you use it directly. KalCode does not charge for, resell or meter provider usage, holds no company provider credentials for your use, and has no KalCode-paid fallback. The same applies to KalVoice: requests that need reasoning run on the provider you choose.
Detection
To find installed providers, KalCode looks for their executables on your PATH and in
documented install locations, then runs only version and status commands, with a timeout. It
reports whether each provider is installed, its version, whether it is signed in where the CLI
exposes that, and what it can do. Detection never changes your machine; installing a provider
only happens when you ask for it.
Isolation
Each provider session runs in its own supervised child process with a sanitized environment. If one provider fails, the others — and your terminals, workspaces and Dashboard — keep running.
One model for every provider
Provider-specific details are translated at the adapter boundary into KalCode's own concepts: normalized events, statuses, approval requests and capabilities. That is what lets the Dashboard, the permission model and KalVoice treat every provider the same way.