Bug: Sub-agent patch created but not applied to parent workspace
other🔴closed
Summary
An exec sub-agent reports a successful commit and generates a patch artifact, but the change does not appear in the parent workspace. The patch exists in session artifacts buttask_apply_git_patchExpected
After a sub-agent completes, the committed change (or its patch) should be applied or easily available to apply viatask_apply_git_patchgit logActual
- The reported commit is not present in the parent workspace.- The file created by the sub-agent is missing.
- A patch artifact does exist in session artifacts.
-
task_apply_git_patchRepro Steps (Generic)
1. Spawn an exec sub-agent to create a new file at repo root and commit it.2. Wait for the sub-agent to finish and report a commit hash.
3. Call
task_apply_git_patch4. Observe it fails with “No git patch artifact found for this taskId.”
5. In the parent workspace, run:
-
git log -5 --oneline-
ls <new-file>6. Observe the commit and file are missing.
7. Inspect session artifacts and find an mbox patch containing the change.
Impact
Sub-agent work appears successful but is not reflected in the parent workspace, and the normal patch application tool cannot find the patch.Notes
This seems to affect exec sub-agents; patch artifacts exist but are not automatically applied or attached fortask_apply_git_patch
