Skip to content

fix(core): require visible worktree choice#301

Merged
shiny-code-bot merged 1 commit into
mainfrom
fix/worktree-warning-harness
Jun 1, 2026
Merged

fix(core): require visible worktree choice#301
shiny-code-bot merged 1 commit into
mainfrom
fix/worktree-warning-harness

Conversation

@shiny-code-bot
Copy link
Copy Markdown
Collaborator

Summary

  • strengthen the model-facing concurrent-checkout notice so the agent must visibly choose an isolated worktree or explain why it is staying before edits
  • add a request-capture regression test proving the notice is sent as a developer message before the user task

Validation

  • cargo test -p code-core --test active_session_warnings concurrent_checkout_notice_in_model_request_requires_visible_worktree_choice
  • cargo test -p code-core --test active_session_warnings
  • ./build-fast.sh

Follow-up

  • Open a follow-up issue to prove the behavior in the exec/TUI harness and decide whether stronger product-level enforcement is warranted.

@shiny-code-bot shiny-code-bot merged commit b23d087 into main Jun 1, 2026
1 check passed
@shiny-code-bot shiny-code-bot deleted the fix/worktree-warning-harness branch June 1, 2026 15:48
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.

2 participants