Add “Commit & settle” and “Commit, push & settle” Git quick actions

[Mosaab-Emam]

Problem / use case

When I finish a coding task, I often want to save or publish the changes and immediately settle the conversation. In the October 4 nightly desktop UI, the workspace Git control already offers Commit, Push, and Create PR, with contextual combined actions such as “Commit & push” and “Commit, push & PR.” Settling the thread still requires a separate action elsewhere.

For example, after reviewing a small fix, I want to commit and push it, then move that finished conversation out of my active list. Repeating the separate settle step across several completed threads adds friction and makes it easy to leave finished work in the inbox.

Proposed behavior

Add explicit variants of the existing Git actions that settle the current thread after the selected workflow succeeds:

Action	Sequence
Commit & settle	Commit → settle this thread
Commit, push & settle	Commit → push → settle this thread
Push & settle	Push existing local commits → settle this thread
Commit, push, create PR & settle	Commit → push → create/link PR → settle this thread

The first two would be a useful initial scope. The PR variant would help when opening the PR completes my work in the conversation, even though review continues on GitHub.

These could live in the existing dropdown, or use a “Settle thread after success” option in the Git action dialog if that keeps the menu simpler. Keep the current Git-only actions available; settling should be an explicit choice for this invocation.

Why this fits Orchestrator V2

The first V2 nightly release notes explicitly include the built-in T3 Code MCP and list settling threads among its capabilities. The current t3_thread_organize tool supports action: "settle", and its handler dispatches the existing thread lifecycle command.

This suggests composing the existing Git workflow with the existing settlement operation. It need not require a model prompt or an MCP round trip from the UI. The existing Git action selection already handles contextual combined actions.

Expected details

• Settle only after every selected Git step succeeds. Cancelling a dialog or failing a commit, push, or PR creation leaves the thread active.
• Apply normal Git confirmations and thread settlement rules. Re-check the originating thread at completion, especially if work resumes during the Git operation; do not interrupt work just to settle it.
• If Git succeeds but settlement is rejected, report the partial success clearly and leave the thread active. Retrying settlement should not repeat the successful Git steps.
• Use normal settlement behavior: preserve conversation history and PR links, with the existing ability to un-settle. A PR variant does not merge or close the PR.

I searched existing issues, PRs, and Ideas discussions for commit/push plus settlement and did not find a matching proposal. This request concerns the desktop/web Git quick actions observed in the nightly UI.