Skip to content

fix(sshx): expose bounded Codex overload diagnostics - #1078

Merged
macstudio-3[bot] merged 1 commit into
devfrom
fix/sshx-issue-1077
Nov 4, 2026
Merged

macstudio-3[bot] merged 1 commit into
devfrom
fix/sshx-issue-1077

Conversation

@macstudio-3

@macstudio-3 macstudio-3 Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Problem

A Codex carrier can spend the whole caller allowance reconnecting to an overloaded upstream and return only CARRIER_EXIT_NONZERO, leaving the caller unable to distinguish an unavailable execution without opening worker reasoning.

Change

  • Project a bounded, sanitized execution_failure object after an invoked nonzero carrier.
  • Recognize only the exact terminal Codex overload messages; keep malformed, unknown, truncated, scanner-failure, and zero-exit cases fail-closed.
  • Preserve opaque logs, artifact/completion semantics, retry/fallback ownership, teardown, and caller-owned time limits.
  • Add synthetic carrier coverage for classification, sanitization, bounded tail scanning, unavailable projection, and unchanged completion checks.

Validation

  • python3.12 skills/sshx/tests/test_run_codex_worker.py (65 tests)
  • python3.12 -m unittest discover -s skills/sshx/tests -p 'test_*.py' (252 tests)
  • python3.12 .github/tests/test_repository_docs.py (9 tests)
  • bash -n skills/sshx/scripts/run-codex-worker.sh
  • git diff --check

Closes #1077

@macstudio-3
macstudio-3 Bot merged commit 47df653 into dev Nov 4, 2026
6 checks passed
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.

Expose upstream Codex overload as compact failure diagnostics without opening worker reasoning

0 participants