Supported Harnesses

Every harness on this page is supported. The Support column describes how the integration is maintained and how urgently the Omnigent team responds when it breaks; it does not indicate whether the harness works.

Support

A Community-supported harness can become Maintained or Fully supported as it gains dedicated integration coverage, CI testing, and active maintenance from the Omnigent team.

Execution modes

Most coding agents can run in one of two modes:

Native TUI harnesses need tmux

Native TUI harnesses run in tmux on the host, so the host needs tmux 3.3 or newer. When tmux is missing, older than 3.3, or doesn't report a version Omnigent can read, a native harness whose CLI is otherwise installed and signed in shows needs tmux in the new-chat picker and in Settings → Harnesses. Problems with installing, updating, or signing in to the CLI show first; the tmux badge appears only once the CLI itself is ready. New sessions can't start on that harness, and Smart Routing doesn't pick it, until tmux is fixed.

To fix it:

  1. Open Set up tmux on the harness in Settings → Harnesses, or use the setup action in the new-chat picker.
  2. Install or upgrade tmux on the host. On macOS, run brew install tmux (or brew upgrade tmux if an older version is installed). On Linux, use your package manager. Check that tmux -V works in a terminal.
  3. Press Check again. If you don't, the host picks up tmux the next time it refreshes harness readiness, about a minute later.

The desktop app keeps the PATH it started with. If tmux was installed into a directory that wasn't on that PATH, quit and reopen the Omnigent app. For a host started from the CLI, restart it from a shell where tmux -V works.

If you sign in or save a credential for a native harness on a host without a usable tmux, the credential is saved and the setup dialog moves straight to the tmux step.

Harnesses

HarnessIDs and aliasesDirect executionNative TUISupportRepository
Claude Codeclaude-sdk (claude), claude-nativeYesYesFully supported—
Codexcodex, codex-nativeYesYesFully supported—
OpenAI Agents SDKopenai-agents (openai-agents-sdk)YesNoFully supported—
CopilotcopilotYesNoMaintained—
Cursorcursor, cursor-nativeYesYesMaintained—
OpenCodeopencode-native (opencode)NoYesMaintained—
Pipi, pi-nativeYesYesMaintained—
Antigravityantigravity, antigravity-nativeYesYesCommunity-supported—
Devindevin-native (devin, native-devin; devin-acp removed in 0.14)NoYesCommunity-supported—
Hermeshermes, hermes-nativeYesYesCommunity-supported—
Kimikimi (kimi-code), kimi-nativeYesYesCommunity-supported—
Kirokiro-nativeNoYesCommunity-supported—
Qwen Codeqwen (qwen-code), qwen-nativeYesYesCommunity-supported—
Rovo Devrovo (rovo-cli)YesNoCommunity-supportedshbhmrzd/omnigent-rovo
ZCodezcode (z-code)Headless print modeNoCommunity-supportedanxkhn/omnigent-zcode

Pi is a headless multi-model worker that runs on any gateway model — ideal for review, exploration, and read-heavy tasks delegated by a supervisor agent.

ZCode requires the separate community plugin and a configured ZCode CLI. See the plugin README for installation, supported features, and print-mode limitations.

Harnesses supported via ACP

Some built-in harnesses use Omnigent's ACP integration under the hood rather than having a separate support designation.

HarnessIDs and aliasesDirect executionNative TUI
Goosegoose, goose-nativeYesYes
Grok Buildgrok (grok-build)YesNo
JcodejcodeYesNo

See Custom ACP agents for ACP configuration details.

See Configuration to set up and run one of these harnesses.