Skip to content

fix: keep rescue task calls in foreground#214

Draft
lttlin wants to merge 1 commit intoopenai:mainfrom
lttlin:fix/codex-plugin-cc/198-rescue-worktree-background
Draft

fix: keep rescue task calls in foreground#214
lttlin wants to merge 1 commit intoopenai:mainfrom
lttlin:fix/codex-plugin-cc/198-rescue-worktree-background

Conversation

@lttlin
Copy link
Copy Markdown

@lttlin lttlin commented Apr 13, 2026

Problem

codex:codex-rescue can orphan Codex runs in worktree isolation when the rescue agent backgrounds its single task Bash call. Claude Code cleans up the temporary worktree as soon as the agent returns, leaving Codex running in a deleted directory.

Root Cause

The rescue forwarding instructions still allow backgrounding the inner codex-companion.mjs task ... Bash call, and the command-contract tests do not enforce that the inner task must always run in the foreground.

Fix

Update the rescue agent and runtime skill to require foreground execution for the inner task Bash call in all cases. --background and --wait remain outer Claude-side controls, but they no longer authorize run_in_background: true on the inner task invocation.

Validation

  • node --test --test-name-pattern='rescue command absorbs continue semantics|internal docs use task terminology' tests/commands.test.mjs
  • Note: node --test tests/commands.test.mjs still has an unrelated pre-existing failure in the result and cancel commands are exposed as deterministic runtime entrypoints assertion on main

Closes #198

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.

[BUG] codex:codex-rescue hangs in worktrees when run_in_background is used

1 participant