You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 153bd63
Browse filesBrowse the repository at this point in the historyBrowse files
- Hook: the dispatched-token branch now emits the full watcher instruction
(buildWatcherContext) instead of a bare "poll /codex:status", matching the
state-inference fallback; removed the now-unused buildDispatchedContext.
- Companion: handleTask now rejects conflicting --background + --wait with an
error, mirroring the --resume/--fresh guard (PR #346 review P2 — previously
--background silently won, ignoring the explicit foreground --wait).
Tests: 101/101.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Copy file name to clipboardExpand all lines: plugins/codex/scripts/codex-rescue-completion-hook.mjs
+1-5Lines changed: 1 addition & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -26,10 +26,6 @@ function buildWatcherContext(jobId) {
26
26
return`codex-rescue background job ${jobId} is RUNNING — there is no automatic push notification. To be notified, arm a watcher: run this via the Bash tool with run_in_background=true: node "${COMPANION_SCRIPT_PATH}" status ${jobId} --wait --timeout-ms 1800000 — it blocks until the job is terminal, then exits and re-invokes you. If it returns and the job is still running, re-arm the same command. Do NOT treat the job as done until the watcher reports a terminal status.`;
27
27
}
28
28
29
-
functionbuildDispatchedContext(jobId){
30
-
return`codex-rescue dispatched background job ${jobId}. No automatic notification will arrive; poll /codex:status ${jobId}.`;
0 commit comments