Skip to main content
When your agent is defined as markdown in a coding-agent harness — its system prompt, config, and instructions as files in your repo — Helix applies approved fixes by editing those files and opening a pull request on GitHub. Supported harnesses include Claude Code, Codex, OpenCode, and the Pi family (Pi, Oh My Pi, Hermes).

Claude Code

Agents defined in .claude/agents/*.md.

Codex

Agents defined as Codex markdown / TOML.

OpenCode

Agents defined as OpenCode markdown.

Pi

Agents defined for the Pi runtime.

Oh My Pi

Agents defined for Oh My Pi.

Hermes

Agents defined for the Hermes runtime.

​
How a fix lands

Helix never writes to your repo directly. After Diagnose ranks a remedy and you approve it:
  1. Helix prepares the change on a branch.
  2. It opens a GitHub pull request with the diff.
  3. You review and merge — the change is yours to accept.
Every apply is approval-gated. Helix proposes; GitHub is where you accept. Nothing lands on your default branch without your merge.
Declare a harness target in your config:
.mutagent/config.yaml
Building an agent as code instead of markdown? See code targets.