chore: verify --worktree agent isolation after CLI 2.1.53 fix #161

Closed
opened 2026-02-25 08:51:28 -08:00 by hikari · 0 comments
Owner

Context

Claude CLI v2.1.53 fixed a bug where --worktree was sometimes ignored on first launch. Hikari Desktop uses isolation: "worktree" in agent definitions to give agents isolated copies of the repository.

Risk

Prior to 2.1.53, the first agent launched in a session may not have received proper worktree isolation, potentially causing agents to share a working directory unintentionally.

Acceptance Criteria

  • Update local Claude CLI to v2.1.53+
  • Test that agent tasks with isolation: "worktree" correctly receive a separate worktree on first launch
  • Verify the worktree is cleaned up after the agent completes
  • Update the CLI version noted in MEMORY.md to 2.1.53

This issue was created with help from Hikari~ 🌸

## Context Claude CLI v2.1.53 fixed a bug where `--worktree` was **sometimes ignored on first launch**. Hikari Desktop uses `isolation: "worktree"` in agent definitions to give agents isolated copies of the repository. ## Risk Prior to 2.1.53, the first agent launched in a session may not have received proper worktree isolation, potentially causing agents to share a working directory unintentionally. ## Acceptance Criteria - [ ] Update local Claude CLI to v2.1.53+ - [ ] Test that agent tasks with `isolation: "worktree"` correctly receive a separate worktree on first launch - [ ] Verify the worktree is cleaned up after the agent completes - [ ] Update the CLI version noted in `MEMORY.md` to 2.1.53 ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-02-26 22:44:32 -08:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#161