Desktop app: 'Commit changes' button sends commit prompt even when the working tree is clean

Description

The Claude Code desktop app shows a Commit changes button just above the message input box. Clicking it sends the canned prompt:

Commit the working tree changes with a sensible message.

The button does not check repository state first: it remains visible/clickable when git status is completely clean (no modified files, no untracked files, no stashes). Each click sends the same prompt, and the model can only respond that there is nothing to commit — wasting a turn (and tokens) each time.

Steps to reproduce

1. Open the desktop app in a git repository with a clean working tree (git status --porcelain outputs nothing).
2. Click the Commit changes button above the text box.
3. The canned commit prompt is sent; the assistant checks the tree and reports nothing to commit.
4. The button can be clicked again with the same result (reproduced 3× in one session).

Expected behaviour

One of:

• Hide or disable the button when the working tree is clean, or
• Have the client check git status before sending and show a "no changes to commit" notice locally instead of sending the prompt.

Environment

• Claude Code 2.1.220 (desktop app)
• Windows 11 Home 10.0.26200
• Git 2.55.0.windows.3, repo on a feature branch with all work committed and pushed

🤖 Filed with Claude Code at the user's request