Skip to content

fix: reconcile routing host disablement - #79

Merged
pacphi merged 3 commits into
mainfrom
fix/routing-host-disable-semantics
Jul 29, 2026
Merged

fix: reconcile routing host disablement#79
pacphi merged 3 commits into
mainfrom
fix/routing-host-disable-semantics

Conversation

@pacphi

@pacphi pacphi commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Summary

Fixes #73: excluding a routing host now performs a complete, ownership-safe disable rather than only flipping its config flag.

  • prune disabled hosts from persisted routes and escalation ladders
  • warn before removing user-pinned routes
  • project only explicitly configured routes into AQE, avoiding default-route reintroduction
  • prune stale agentic-kit-curated AQE overrides while preserving foreign overrides
  • retire only marker-owned Codex MCP bridges; re-enable converges them normally
  • document the unified disable semantics

Verification

  • pnpm run check
  • sandboxed command tests assert the exact owned Codex MCP removal calls

This follows #77 and closes the disable-semantics gap before generalized routing can safely expand.

@pacphi
pacphi merged commit 5719a40 into main Jul 29, 2026
11 checks passed
@pacphi
pacphi deleted the fix/routing-host-disable-semantics branch July 29, 2026 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

x provider pick: excluding a routing host (codex) leaves seeded routes, agentOverrides, and MCP bridges live — one disable semantics for all hosts

1 participant