[Feature Request] User setting to control worktree toggle default

Resolved 💬 1 comment Opened Apr 20, 2026 by BarriePocock Closed May 27, 2026

Summary

The "worktree" toggle in the Claude Code desktop app's chat input bar defaults to ON for every new chat. There's no user-accessible setting to change this default, creating repeated friction for users who prefer direct-branch workflows.

Environment

  • Claude Code desktop app on Windows 11
  • Anthropic Max plan
  • Workflow: solo developer, local-first, direct-push on a monorepo

Current Behaviour

Every new chat session opens with the worktree toggle checked. Must be manually unchecked per session.

Investigation

Found tengu_worktree_mode flag in ~/.claude.json. Editing it to false gets auto-reverted by the app on next write — confirming it's server/cache-managed rather than user-configurable. No equivalent setting exists in ~/.claude/settings.json or project-level .claude/settings.local.json.

Requested Feature

A user setting at user or project scope, e.g.:

{
  "ui": {
    "worktreeDefault": false
  }
}

Or equivalent. Ideally also respects the user's last-used toggle state within a project as a sticky preference.

Use Case

Solo developer with a local-first workflow. Worktrees are unnecessary — they create ephemeral claude/* local branches that add visual noise to git branch output even though they never reach the remote. Direct operation on the checked-out branch matches the mental model better.

Additional Notes

Worktree branches are local-only (not pushed to origin), so this is purely a user-preference / UI-default issue, not a workflow-correctness issue. The feature is useful and should remain available — just not be the default for everyone.

Thanks for considering!

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗