Skip to content

fix(operator): disable Codex hooks at launch boundary - #64

Closed
urbanplanningpros wants to merge 4 commits into
devfrom
fix/operator-codex-hook-remote-control-guard-20260729
Closed

fix(operator): disable Codex hooks at launch boundary#64
urbanplanningpros wants to merge 4 commits into
devfrom
fix/operator-codex-hook-remote-control-guard-20260729

Conversation

@urbanplanningpros

Copy link
Copy Markdown
Owner

Issue for this PR

Related upstream issue: openai/codex#35929

Repository issues are disabled, so a local issue could not be created.

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Adds a guarded Codex launcher that forces lifecycle hooks off and rejects CLI or config attempts to re-enable them. This prevents root/plugin hook-order ambiguity from becoming a prompt-capture boundary. It also documents a dedicated, canary-only protocol for the newly documented experimental CLI remote-control workflow.

How did you verify your code works?

Run:

bun scripts/operator/codex-hook-policy-safe-launch-selftest.mjs
bun scripts/operator/codex-hook-policy-safe-launch.mjs --dry-run -- exec --ephemeral -

The self-test checks that --disable hooks is present and that both --enable hooks and [features] hooks = true fail with exit 64.

Screenshots / recordings

Not applicable; no UI change.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@github-actions

Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • Not all checklist items are checked. Please confirm you have tested locally and have not included unrelated changes.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions

Copy link
Copy Markdown

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

@github-actions

Copy link
Copy Markdown

This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new pull request that follows our guidelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant