OpenFolksDocs
Agent engines

Engines

Use the agent subscriptions and CLIs you already have.

OpenFolks does not sell a shared model account. It starts supported engine CLIs on your computer and normalizes their output through the local harness.

Built-in engines

EngineHow you sign inNotes
ClaudeClaude CLI loginStrong tools, approvals, sessions, and local computer use
CodexCodex CLI loginModel discovery, approvals, steering, computer tools
GrokGrok CLI loginACP catalog and session support
CursorCursor Agent CLI login or API keyACP driver with live model discovery
AntigravityGoogle Antigravity CLI loginGoogle consumer engine
OpenCodeExisting OpenCode login or optional API keyZen, Go, third-party, and local models through ACP
HermesHermes CLI loginACP integration
PiPi CLI loginNative driver
OpenRouterOpenAI-compatible API keyAny OpenRouter, Groq, or compatible base URL

You can declare extra driver instances in local configuration. Unavailable engines stay visible with a reason instead of taking down the fleet.

Detection

OpenFolks checks common install directories and the login shell in the background. Restart the app after you install or authenticate a CLI.

If detection fails, set the executable in Settings → Engines. That works for every engine and is the reliable path for version managers, wrappers, custom builds, and Windows installs outside the normal path.

Model selection

The picker groups models by provider and marks defaults. Supported engines can refresh their catalog from the installed CLI. Changing the model affects future turns. It does not rewrite earlier history.

Billing stays with the provider

Your CLI login or API key decides access and cost. OpenFolks does not turn one subscription into another provider.

On this page