AGY, Gemini, Claude, Codex.

Supported launch model

These defaults are starting points. Review each command's permission model before running it on a repository.

Placeholders

• {{prompt}} becomes the implementation or repair prompt.
• {{cwd}} becomes the isolated worktree path.

agent.launchCwd changes the directory used to start the agent. This is useful when an agent keeps authentication state per launch directory. The agent still receives {{cwd}} as its edit location.

AGY with Gemini on Windows

AGY can launch from a separately authenticated directory while --add-dir {{cwd}} grants access to the temporary worktree. That keeps launch-directory authentication without storing the session in the repository.

{
  "agent": {
    "provider": "gemini",
    "command": "agy",
    "args": [
      "--agent", "gemini",
      "--add-dir", "{{cwd}}",
      "--print", "{{prompt}}",
      "--output-format", "json",
      "--mode", "accept-edits",
      "--print-timeout", "300s"
    ],
    "timeoutMs": 330000
  }
}

What the agent is told

• Work only in the isolated worktree.
• Keep acceptance criteria and the Kane test stable.
• Make the smallest production-quality change and run relevant local checks.
• Elenchos will decide verification status from Kane, not from the agent summary.

A repair prompt includes structured Kane failure evidence and the repair attempt number. Authentication failures are reported as agent authentication failures. Refresh the agent's own credentials before retrying.

Select an agent at init

npx elenchos init --force --agent agy

Supported overrides are agy, claude, gemini, and codex. An unsupported value is rejected. If more than one CLI is on PATH, init keeps the choice visible instead of guessing.