Supported agents

The agent CLIs Open Free Max drives — Claude Code, Codex, OpenCode, Gemini, Vibe and Kimi Code — and how provider support is structured.

OFM is bring-your-own-agent. It drives the official CLIs you already have installed and logged in; it never bundles, updates or proxies them.

Supported CLIs

CLIProviderNotes
Claude CodeAnthropicFull session resume by id, naming, fork
CodexOpenAIInteractive CLI
OpenCodeOpen sourceInteractive agent CLI
GeminiGoogleInteractive CLI
VibeMistralInteractive CLI
Kimi CodeMoonshot AIInteractive CLI

Provider adapters

Each provider is described by a small declarative adapter that knows how to:

  • launch the binary in interactive mode (with the right session/resume flags);
  • apply your settings (model, effort, permission mode, allowed tools, MCP config, …) as launch flags — configured once in Settings;
  • read its screen to detect state and confirmation prompts.

Adding a new CLI is one adapter — the rest of the app is provider-agnostic.

Autonomy levels (A / B)

Not every CLI exposes its confirmation prompts identically, so OFM grades providers:

  • Level A — driven (Claude Code): OFM reliably classifies its screen and confirmation boxes, so it can fully auto-resolve and run autonomously per your rules.
  • Level B — assisted (others, initially): the engine still runs them — dispatch, leasing, quota parking — but their confirmations always go to the human queue rather than being auto-answered blindly. No CLI is ever excluded; a level-B provider just asks for a hand more often.

In Plan, the chosen CLI’s level is shown on the campaign form so you know up front whether a batch will run hands-off or surface confirmations.

Authentication

You sign in where you already do — inside each official CLI. OFM never sees your tokens or keys. See Subscription vs API.