auto-routing

Auto Routing for Claude Code

This generated file is the Claude Code-facing runtime skill document. Claude Code slash commands should read this file directly; maintainers edit the source documents listed below instead.

Generated Runtime Composition

Source order:

• ../../docs/skill-core/auto-routing.md
• ../../docs/platforms/claude-code-runtime.md
• ../../docs/platforms/claude-code-auto-routing.md

The sections below are already composed for this platform. Do not ask the runtime model to load another platform's runtime document or invocation syntax.

Source: docs/skill-core/auto-routing.md

Auto Routing

Auto Routing is the manager of the Oh No Harness session toggles. It manages two independent, session-scoped preferences stored in the same config.json: the autoRouting skill-selection toggle described here, and the codexExecutor executor-delegation toggle described under Codex Executor Delegation Toggle below. Both are read at bootstrap/session-start.

Auto Routing (the autoRouting toggle) controls whether a supported platform bootstrap hook adds stronger skill-selection guidance to using-oh-no-harness.

It does not add hidden runtime routing. It only changes persistent user preference for the SessionStart prompt.

Software Development Stage

Auto Routing is a workflow-entry configuration stage, not a software development stage.

Use it to make future sessions more likely to choose the right skill before work starts. It should not gather requirements, plan, edit code, debug failures, clean code, or verify completion.

When To Use

Use when the user asks to:

• enable, turn on, activate, or make skill routing more automatic
• disable, turn off, deactivate, or make skill routing quieter
• check current auto-routing status
• preserve stronger or weaker routing behavior across plugin updates
• enable or disable delegating the executor role's implementation work to Codex (the codexExecutor toggle)
• check current codex-executor delegation status

Do not use as a substitute for skill selection inside the current session — for choosing a workflow skill in the current turn, read and follow using-oh-no-harness.

Platform Behavior

Apply the active platform runtime document before changing settings. Some platforms support persistent bootstrap routing; others can only explain the setting and leave runtime behavior unchanged.

When the active platform supports persistent bootstrap routing, changes take effect on the next bootstrap or session-start event, such as a new session, app restart, clear/reset command, or compaction. Existing session context is not rewritten.

Codex Executor Delegation Toggle

The codexExecutor toggle is the second session toggle this skill manages. When ON, and on a platform whose bootstrap supports delegation, Oh No Harness delegates the executor role's implementation work to Codex instead of the native oh-no-harness:executor, for every executor dispatch path (ralph, ultrawork, systematic-debugging).

Shared facts (all platforms):

• Default OFF. Delegation is opt-in; with the toggle OFF the native oh-no-harness:executor runs and nothing changes.
• Executor role only. When ON, only the executor role is re-bound to Codex. RED authoring, verification, review, and merge stay with the native independent roles.
• Eligibility unchanged. Existing Ralph eligibility remains the sole gate. An already-admitted disjoint executor batch may overlap only at the outer executor-codex agent layer; each inner companion call remains foreground. Ineligible, unknown, or unsafe work stays serial, and fallback and integration remain caller-owned and sequential.
• Best-effort confinement, not a guarantee. Delegated writes are scoped best-effort to the task worktree. The executor transport returns raw Codex output; the caller owns the escape-DETECTION guard, derives the worktree diff, and halts before merge on an unexpected protected-target change. This is DETECTION, not prevention, and is not a sandbox guarantee.
• Manage it with oh-no-config codex-executor on|off|status (see Commands), then restart or clear the session so the bootstrap re-fires (see Response Rules). Whether the toggle produces a runtime effect depends on the active platform (see Platform Behavior and the platform runtime document).

Configuration

The setting is stored outside the plugin cache so updates do not overwrite it.

Preferred location when the active platform provides plugin data:

<platform-plugin-data>/config.json

The bundled scripts/oh-no-config script resolves the data directory; the platform runtime document names the plugin root.

Fallback location when no platform plugin-data directory exists:

${XDG_CONFIG_HOME:-$HOME/.config}/oh-no-harness/config.json

Stored shape (both toggles are independent sibling keys):

{
  "autoRouting": {
    "enabled": true
  },
  "codexExecutor": {
    "enabled": false
  }
}

codexExecutor defaults to OFF (enabled: false). Writing one toggle must preserve the sibling toggle's value; never clobber autoRouting when changing codexExecutor, or vice versa.

Commands

When Bash is available, use the bundled script instead of editing config by hand.

When the active platform runtime document exposes the plugin root:

"<plugin-root>/scripts/oh-no-config" status
"<plugin-root>/scripts/oh-no-config" on
"<plugin-root>/scripts/oh-no-config" off

If the plugin root is not exposed, locate the installed script first according to the active platform runtime document.

script="$(find <platform-plugin-cache> -path '*/oh-no-harness/*/scripts/oh-no-config' -print -quit)"
"$script" status

The same script manages the codexExecutor toggle through the codex-executor subcommand, mirroring the auto-routing verbs:

"<plugin-root>/scripts/oh-no-config" codex-executor status
"<plugin-root>/scripts/oh-no-config" codex-executor on
"<plugin-root>/scripts/oh-no-config" codex-executor off

Response Rules

• For on, enable the setting, report the config path, and tell the user to restart or clear the active platform session before expecting the new behavior.
• For off, disable the setting, report the config path, and tell the user to restart or clear the active platform session before expecting the new behavior.
• For status, report whether auto-routing is on or off and where the setting is stored.
• For codex-executor on, enable the codexExecutor toggle, report the config path, and tell the user to restart or clear the active platform session before the delegation takes effect — the bootstrap re-fires on the next session-start.
• For codex-executor off, disable the codexExecutor toggle, report the config path, and tell the user to restart or clear the session before the change takes effect.
• For codex-executor status, report whether codex-executor delegation is on or off and where the setting is stored.
• When changing either toggle, preserve the sibling toggle's value; do not clobber autoRouting or codexExecutor when writing the other.
• If Bash is unavailable, explain the config file shape without claiming the setting changed.
• Do not invoke workflow skills from this configuration skill.

Source: docs/platforms/claude-code-runtime.md

Claude Code Runtime Rules

This compact platform section is embedded in generated Claude Code-facing skill documents.

Skill Loading

Claude Code-facing public skills live under skills-claude/. Generated skills-claude/<skill>/SKILL.md files compose the matching skill core, this compact runtime section, and any Claude Code skill-specific overlay such as docs/platforms/claude-code-<skill>.md. Slash commands must delegate to the matching generated skill document.

User Approval, Tasks, And Prompting

Use the host's structured question tool when available for approval, preference, scope, or next-step selection; otherwise ask one focused plain-text question and wait. Present options as actions the host agent will take.

When a core skill has a multi-phase approval handoff and the host exposes task tracking, create one task per phase and complete them sequentially.

Keep Claude prompts explicit and sectioned: state scope, non-goals, constraints, approval gates, expected evidence, and output format. Preserve long-running context in artifacts before compaction, task handoff, or subagent dispatch.

Role Dispatch

Dispatch only after the active skill's trigger fires, then read docs/platforms/claude-code.md ## Role Dispatch for the full host contract. Prefer oh-no-harness:<role>, request the whole independent batch before waiting, capture every final result, and clean up only after integration. An approved-plan handoff is dispatch authorization for eligible isolated roles; plugin-agent unavailability uses the documented embedded-role fallback.

Cross-Host Consult Channel

This channel is trigger-loaded, not embedded in every workflow decision. When a named THOROUGH paired-review or Fusion Rescue trigger fires, read and apply docs/platforms/claude-code.md ## Cross-Host Consult Channel before dispatch. Until then, do not preload opposite-host invocation details.

Source: docs/platforms/claude-code-auto-routing.md

Claude Code Auto Routing Rules

This platform overlay is source content for the generated Claude Code-facing auto-routing runtime document, after the shared core and docs/platforms/claude-code-runtime.md.

Preferred config location:

$HOME/.claude/plugins/data/<oh-no-harness-*>/config.json

When CLAUDE_PLUGIN_ROOT is set, use:

"${CLAUDE_PLUGIN_ROOT}/scripts/oh-no-config" status
"${CLAUDE_PLUGIN_ROOT}/scripts/oh-no-config" on
"${CLAUDE_PLUGIN_ROOT}/scripts/oh-no-config" off

The codexExecutor toggle uses the same script with the codex-executor subcommand:

"${CLAUDE_PLUGIN_ROOT}/scripts/oh-no-config" codex-executor status
"${CLAUDE_PLUGIN_ROOT}/scripts/oh-no-config" codex-executor on
"${CLAUDE_PLUGIN_ROOT}/scripts/oh-no-config" codex-executor off

On Claude Code, the shared core's bootstrap/session-start timing applies as the SessionStart event, and the clear/reset command is /clear.

When the codexExecutor toggle is ON, the codex-executor delegation block is injected via SessionStart on Claude Code only. That injected block re-binds the executor role and dispatches oh-no-harness:executor-codex in place of oh-no-harness:executor. Turning the toggle on or off takes effect only after the SessionStart event re-fires (a new session or /clear).