[FEATURE] Feature request: Setting to hide the "Commit changes" button in source control chip

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

Claude Code's input area shows a source control chip displaying the current branch diff (e.g. "main ← mobile-app +53180 -61008") with an always-visible "Commit changes" button.

When working on a branch with many uncommitted changes across multiple sessions, this always-visible button creates risk of accidental clicks that commit unintended work. There is currently no setting to hide or disable it.

Power users who prefer explicit git control — either via the terminal or by asking the agent to commit — would like to hide the button entirely, so the only path to a commit is a deliberate, explicit one.

Proposed Solution

Add a setting in settings.json to hide the source control chip / Commit button. For example:

{
  "ui": {
    "showSourceControlChip": false
  }
}


### Alternative Solutions

Workarounds currently available:
1. Telling the agent "never commit without my explicit permission" — works for the agent but doesn't prevent manual clicks on the UI button.
2. Using `git` commands directly in a separate terminal — doesn't remove the button from Claude Code's UI.
3. Setting up a `pre-commit` git hook that rejects commits matching certain criteria — heavyweight, affects all git tooling, not just Claude Code.

None of these hide the UI element itself. The cleanest solution is a settings toggle.


### Priority

Medium - Would be very helpful

### Feature Category

Other

### Use Case Example

Scenario:
1. I'm on a long-lived feature branch (`mobile-app`) with ~50 commits of uncommitted work staged across many files.
2. I run two Claude Code sessions in parallel, each making targeted edits to different files.
3. Between sessions, I review diffs manually and decide what to commit and when — sometimes I stash, sometimes I reset, sometimes I commit a subset.
4. The "Commit changes" button is always visible in the input chip. A single accidental click commits EVERYTHING staged, including work I hadn't planned to commit yet.
5. With a `"ui.hideCommitButton": true` setting, the button would be hidden. I'd commit exclusively via `git` in my terminal or by explicitly asking the agent. No accidental commits possible.

This would save me from having to `git reset HEAD~1` (or worse, untangling a mixed commit) after accidental clicks.


### Additional Context

<img width="817" height="249" alt="Image" src="https://github.com/user-attachments/assets/f5ac5f59-4b50-4fdb-ace0-2960390738c5" />