Built-in Auto-Commit Safety Settings for Worktree Workflow

Resolved 💬 3 comments Opened Jan 4, 2026 by edumusikse Closed Feb 19, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Anthropic Feedback - Auto-Commit Feature Request

Subject: Feature Request - Built-in Auto-Commit Safety Settings for Worktree Workflow

Problem: The Mac app and Claude Code documentation actively promote using Git worktrees for parallel development sessions.

However, this workflow creates significant data loss risk:

  • Users are forced into a more complex Git workflow without built-in safety nets
  • Uncommitted work in worktrees can be easily lost when switching contexts
  • Users must discover and manually configure hooks to protect their work
  • This puts the burden on users to understand Git internals AND hook configuration

Proposed Solution

Add auto-commit as a built-in setting in Claude Code with options like:

Auto-commit after each file edit (maximum safety)
Auto-commit when session ends
Auto-commit every N minutes
Prompt me to commit when closing session (default)
Manual commits only (advanced users)

Why this matters:

  • Data loss from uncommitted worktree changes is a real risk
  • If you're promoting worktrees as best practice, the safety features should be first-class
  • New users shouldn't need to be Git experts to avoid losing work
  • Current solution requires manual JSON editing and understanding of hooks system

Example: VSCode has auto-save settings. IntelliJ has local history. Claude Code should have auto-commit settings when working in Git repos. The hooks system exists and works great - just expose it through the UI with sensible defaults.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗