Helios / Providers

Use the agent that fits the task.

Helios brings six provider integrations into the same desktop. Each keeps its own model access, authentication and execution behaviour.

You need a version that includes the provider you want. The current GitHub release includes all six; the default APT channel may be older. Check install channels.

Provider	Helios connects through	Account or key	Where to begin
Claude Code	Official `claude` CLI	Claude CLI sign-in	Claude setup
OpenAI Codex	Persistent Codex App Server	Codex account or API key	Codex setup
Gemini	Google Antigravity `agy` CLI	Google account through Antigravity	Google setup
Muse Code	`muse serve`	Muse account or Meta API key	Muse setup
Kimi Code	`kimi acp`	Kimi Code membership sign-in	Kimi setup
OpenRouter	Helios’s OpenRouter agent loop	OpenRouter API key	OpenRouter setup

Anthropic

Claude Code, with a desktop around it.

Install the official claude CLI and complete its sign-in in a terminal. Helios discovers the binary and drives the CLI’s streaming interface. It uses Claude Code’s existing context and session history.

The conversation toolbar exposes supported model, effort and permission controls. Native tool approvals, questions and Plan mode remain tied to Claude’s own protocol. A supported live model switch can take effect in the running chat.

Official Claude Code setup · Helios provider guide

OpenAI

Codex sessions through App Server.

Install the official Codex CLI, run codex login and check the detected account in Helios Settings. API-key sign-in is also available through Settings; merely exporting OPENAI_API_KEY does not sign Helios’s Codex session in.

npm install -g --prefix ~/.local @openai/codex
codex login

Helios binds to a persistent Codex App Server for native sessions, approvals, plans and compaction. Available models, effort levels and sandbox settings depend on the installed CLI and account.

Official Codex CLI guide · Helios user guide

Google

Gemini through Google Antigravity.

Install the official agy CLI, open it in a terminal and sign in to your Google account. Helios discovers the models reported by agy models.

This is the Antigravity integration, not a generic Gemini API-key route. Its execution choices are Sandboxed, Accept edits, Bypass and Read only. The headless integration cannot display or answer interactive CLI approval requests, and it uses its own browser rather than Helios’s per-session browser tools.

Google setup and a reviewable first trial →

Muse Code through its native service.

Install Muse Code and run muse login, or enter a Meta API key in Helios Settings. Helios uses muse serve for sessions, native questions, approvals and background activity.

An environment META_API_KEY takes precedence over stored account sign-in. Check the active route before starting a session if you intended to use a subscription.

Account and provider settings in the user guide →

Moonshot AI

Kimi Code membership, through ACP.

Install the official Kimi Code CLI and complete kimi login. Helios connects through kimi acp and discovers the models available to that signed-in membership.

The integration includes native models and thinking controls, resume and fork, images and resources, tools, approvals and MCP forwarding. Account quota windows and audio are not exposed by the current integration. Kimi through OpenRouter is a separate API route.

Kimi membership setup and verification →

OpenRouter

A live model catalogue, with your API key.

Enter an OpenRouter API key in Helios Settings. Helios runs its own coding-agent loop against models from the live catalogue, rather than launching a provider CLI.

Reasoning controls follow the selected model’s advertised capabilities. Tool support, context size, pricing and reasoning behaviour vary by model. OpenRouter uses metered API billing and Helios applies its own per-Work allowance and tool-round limits.

OpenRouter configuration →

What is shared?

The session list, conversation view and project workspace provide a consistent place to follow a task. The model picker and execution panel reflect the selected provider’s capabilities.

Claude, Codex, Muse, Kimi and OpenRouter can receive Helios browser tools when their integration supports them. Gemini’s Antigravity route uses its own browser.

What still varies?

Model availability, authentication, native approvals, context reporting, reasoning controls and billing. A permission label on one provider does not promise the same isolation on another. Helios does not include a model subscription.

Read the trust model →

Start with one project

Bring your next task to Helios.

Install the app, connect one provider and choose a project folder.

Install Helios