cortex-reroute

/cortex-reroute

Flag the most recent route in the current project and agent session as outcome=corrected and record the route the user wanted instead. This is the highest-quality training signal for Phase 3 (similarity bias) when it activates.

When to invoke

• User types /cortex-reroute "<corrected route>" explicitly
• User says "reroute" / "actually use X" / "we should've used Y" right after a routing line
• User says "the right route was..." / "should've been..." / "redo with..."
• Any clear post-hoc correction of the last logged route

What to do

Step 1 — Mark the last entry as corrected

Resolve the state directory from CORTEX_HOME, then CLAUDE_DIR, then $HOME/.claude, matching the CLI and installer. Keep a custom override exported in the agent's environment.

cortex_state_dir="${CORTEX_HOME:-${CLAUDE_DIR:-$HOME/.claude}}"
python3 "$cortex_state_dir/bin/cortex" reroute --to "<the route the user wanted>"

The CLI:

• Appends a correction for the latest route in the current project and session
• Stores the user's preferred route in user_correction
• Prints the before → after delta

If the CLI cannot identify that session, inspect cortex history <task_hash> and pass the intended route's exact ID with --ref. Never pick another project's route or infer a target from an ambiguous legacy ID.

Step 2 — Log the new route

If the user wants the corrected route to actually run now, log it as a fresh entry with --redirect-from so the two are linked:

cortex_state_dir="${CORTEX_HOME:-${CLAUDE_DIR:-$HOME/.claude}}"
python3 "$cortex_state_dir/bin/cortex" log \
  --task "<same task as before>" \
  --class <class> \
  --system <new system> \
  --pattern <new pattern> \
  --agent "<new agent>" \
  --tier <new tier> \
  --tier-reason "<...>" \
  --system-reason "User redirected from <old route>" \
  --redirect-from "<old route>"

The redirect_from field links the corrected entry to the new one — Phase 3 uses this to learn "Cortex picked X, user wanted Y" deltas.