Skip to content

Comments

fix(taskctl): commitTask uses explicit worktree path and verifies commit succeeded (#277, #278, #279)#280

Merged
randomm merged 2 commits intodevfrom
fix/issue-279-commit-task-directory-verification
Feb 20, 2026
Merged

fix(taskctl): commitTask uses explicit worktree path and verifies commit succeeded (#277, #278, #279)#280
randomm merged 2 commits intodevfrom
fix/issue-279-commit-task-directory-verification

Conversation

@randomm
Copy link
Owner

@randomm randomm commented Feb 20, 2026

Fixes #277, #278, #279

Changes

Bug 1 fix (pulse.ts ~line 586): Explicit worktree path in ops prompt

Changed ops prompt from 'Commit all changes in the current directory' to explicitly name the worktree path and instruct @ops to use it as workdir parameter for all bash commands. The bash tool uses Instance.directory (project root) as default cwd — session.directory is ignored. Making the path explicit forces @ops to pass workdir correctly.

Bug 2 fix (pulse.ts ~line 631): Verify commit succeeded before marking done

After @ops session completes, read final assistant message via MessageV2.stream() and check for:

  • Commit hash (7-40 hex chars) → success
  • 'nothing to commit' → escalate with error (developer changes not found in worktree)
  • Neither found → escalate with unclear output error

Previously task was unconditionally marked stage:done even when git reported 'nothing to commit', silently losing all developer work.

@randomm randomm merged commit 2f19929 into dev Feb 20, 2026
1 check passed
@randomm randomm deleted the fix/issue-279-commit-task-directory-verification branch February 20, 2026 21:01
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.

fix(taskctl): @ops commit session runs in wrong directory — changes not committed

1 participant