Skip to content

fix(codex): scope app-server lifecycle to each invocation - #1016

Open
GigiTiti-Kai wants to merge 5 commits into
fujibee:mainfrom
GigiTiti-Kai:fix/codex-invocation-scope
Open

fix(codex): scope app-server lifecycle to each invocation#1016
GigiTiti-Kai wants to merge 5 commits into
fujibee:mainfrom
GigiTiti-Kai:fix/codex-invocation-scope

Conversation

@GigiTiti-Kai

@GigiTiti-Kai GigiTiti-Kai commented Aug 30, 2026

Copy link
Copy Markdown

Summary

  • supervise one Codex app-server per project and invocation scope, then stop only the children owned by that invocation
  • route role bridges to the exact scoped server and recorded thread while leaving malformed requests unread
  • close the reviewed race after the child lock and cover duplicate-scope and malformed-request boundaries

Verification

  • full Bats suite: 1740/1740 passed with AGMSG_CODEX_SHIM_DISABLE unset for the Codex harness
  • focused new regressions: 3/3 passed
  • Codex bridge launcher suite: 79/79 passed
  • Codex monitor suite: 23/23 passed
  • resume, delivery, and shim suites: 253/253 passed
  • bash -n and git diff --check passed

Local review evidence

  • surface/class: Codex standard T2; fresh reviewer stalled twice with no progress events, so the runbook fallback was used
  • BASE_SHA: 660f67b
  • HEAD_SHA: 14855dd
  • structured self-review covered ownership, signal authority, scoped request validation, lock races, peer isolation, cleanup, and test coverage
  • P0/P1: none; no findings required a code change
  • earlier three-commit read-only review findings were closed by the final commit and its focused regressions

Add opt-in invocation supervision that captures the TUI, app-server, and bridge launcher, then reaps only those owned processes and exact scoped artifacts.

🤖 Generated with Codex
Bind scoped SessionStart requests and dispatchers to the derived server key, exact project, and recorded thread while preserving legacy project-wide routing.

🤖 Generated with Codex
Document the opt-in ownership boundary, exact routing contract, legacy behavior, and SIGKILL recovery limit for invocation-scoped monitoring.

🤖 Generated with Codex
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