Add guarded codex-exec dispatch pipeline#5
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0a86b8ee6e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const statusLines = getGitStatusShort(preview.cwd); | ||
| const changedFiles = statusLines.map(parseChangedFile); | ||
| const runtimeOutputFiles = changedFiles.filter(isWorkerRuntimeOutputPath); | ||
| const scopeWarnings = findScopeWarnings(preview.task.id || "unknown-task", changedFiles, preview.task); |
There was a problem hiding this comment.
In the worker execution post-check, scope validation is derived only from git status --short, which reports uncommitted/untracked files but not files already committed on the worker branch. If codex exec commits its changes before returning, a worker can add or modify files outside allowedFiles or inside forbiddenFiles and still get Scope: OK / Status: PASS; I reproduced this by having a worker commit secret.txt while the task only allowed a.txt, and the check only saw .cewp-worker-output/. The guard needs to include committed branch changes as well as the working tree before deciding the worker stayed in scope.
Useful? React with 👍 / 👎.
Summary
Adds guarded codex-exec execution support for Coordinator Mode.
Added
.cewp-worker-output/Safety
--yesVerification
npm pack --dry-runpassed