v1.8.1 — Surface Codex Backend Errors

What's New

This release makes Codex backend failures visible instead of silent, and stops the static model allowlist from giving false confidence.

Fixed

• Codex backend failures are no longer silent (#28) — When a Codex instance hits a backend error (e.g. the Bedrock proxy 404ing an unknown model, a JSON-RPC error, or a stream failure), the spawn_codex / send_to_instance result now reports status: "failed" with the terminal error surfaced in error / error_message, and get_instance_status exposes the same message. Previously these returned status: "completed" with an empty response and error_message: null, only diagnosable by scraping the tmux pane. Empty output with no detectable error is also flagged as a failure.

Changed

• Removed the static model allowlist (#28) — spawn_claude / spawn_codex no longer validate model names against a hard-coded list. Any model string is forwarded to the underlying CLI/backend as-is; only the provider default (from config/models.yaml) is used when no model is given. The allowlist produced false rejections and false confidence for Codex models, whose valid ids are served by an AWS Bedrock proxy that changes independently of Madrox. Codex Bedrock routing and the new error behavior are documented in docs/TROUBLESHOOTING.md.

Upgrade Notes

No breaking changes.