Skip to content

fix: recover expired runtime approvals - #22

Merged
Codename-11 merged 1 commit into
mainfrom
codex/runtime-approval-expiry-recovery
Jul 13, 2026
Merged

Codename-11 merged 1 commit into
mainfrom
codex/runtime-approval-expiry-recovery

Conversation

@Codename-11

Copy link
Copy Markdown
Owner

Summary

  • classify Hermes 404s as missing provider runs instead of successful completion
  • keep polling provider-backed WAITING approvals so swept sessions self-reconcile
  • when an approval discovers expiry, retire the orphan and atomically start a fresh same-agent/same-mode run
  • tell the operator explicitly that the old approval was not applied and may be requested again

AXI-102 evidence

Forge retained WAITING run cmrjhkjbf037mo1089vzolecc, but Hermes returned run_not_found for provider run run_10446861a003426f88b2c692d30a2542. The previous worker only polled ACTIVE runs, leaving the approval immortal.

Verification

  • pnpm ci:local
  • Vitest: 1,167 passed, 1 skipped
  • fresh Next.js production build passed
  • Playwright: 37 passed

@Codename-11
Codename-11 merged commit a75667c into main Jul 13, 2026
2 of 3 checks passed
@Codename-11
Codename-11 deleted the codex/runtime-approval-expiry-recovery branch July 13, 2026 21:17
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.

1 participant