Add version control command center

[Quicksaver]

Summary

Adds a Git-backed Version Control command center to the web right panel and a native mobile route. It is scoped to the active project/repository cwd, works from draft or existing conversations once repository context is available, and keeps Git operations server-authoritative across browser, desktop, VS Code, and remote clients.

The panel focuses on actionable repository work rather than being a full Git dashboard: dirty working trees, local branch sync state, stashes, remotes, sibling worktrees, likely fork branches, and open change-request bases.

What Changed

• Added SOURCE_CONTROL.md as the branch-specific behavior and validation reference for the Version Control panel.
• Added server-side SourceControlPanelService RPC support for snapshots, branch/stash/commit/compare data, selected-file commit and stash flows, discard operations, branch actions, remote actions, and provider-derived PR/MR base checks.
• Extended GitHub, GitLab, Azure DevOps, and Bitbucket source-control provider plumbing so actionable rows can account for open change-request bases while preserving bounded provider diagnostics.
• Added live VCS refresh support through VcsStatusBroadcaster and VcsLocalWatch, including ref-counted local watchers, .git/ event filtering, gitignore-aware suppression, explicit local refreshes, and sibling worktree watcher retention.
• Added the React Version Control panel UI with Actionable and Remotes sections, working-tree file selection, inline diffs, branch/stash/commit rows, searchable compare bases, guarded destructive actions, context menus, manual fetch controls, and a conservative five-minute Actionable remote fetch.
• Added a native mobile Version Control route from the Git menus with touch-oriented Actionable and Remotes sections, selected-file operations, branch/stash/remote actions, dedicated review-diff navigation, and stale-result protections.
• Centralized right-panel add-surface action metadata so the empty state and add menu share the same Version Control surface gating and action model.
• Added dirty sibling worktree rows and cwd-scoped right-panel File previews so Git operations and file reads target the checkout that owns the displayed changes.
• Hardened branch sync behavior around same-name remote tracking, fork branches, open PR/MR base branches, local-only publishing, diverged branch actions, branch names containing slashes, and branch worktree cwd routing.
• Added concurrency and stale-result protections through per-target operation state, per-thread metadata sequencing, expectedBranch write guards, and environment/thread/cwd-scoped panel state.
• Hardened self-hosted GitLab open-MR discovery by passing a full project URL to glab mr list --repo instead of an ambiguous scheme-less host/path locator, without duplicating a configured base-URL path prefix already present in the remote path.
• Preserved typed Git and provider failures as bounded, sanitized diagnostics so process, authentication, API, and command-output causes remain distinguishable without exposing unbounded error payloads.
• Hardened working-tree handling for renamed files, quoted porcelain paths, mixed staged/unstaged rows, selected-file commit pathspec semantics, discard failures, generated commit failures, and branch deletion resolution.
• Hardened review follow-ups for source-control thread metadata sequencing after a thread is closed/reopened and default compare ref selection for repositories whose checked-out default branch is not named main or master.
• Hardened right-panel fallback behavior so an unavailable active Source Control surface falls back to another visible surface instead of forcing the empty right-panel state.
• Hardened cached Version Control panel restores so cached snapshots show the refresh indicator while revalidating, and restored expanded branch/stash rows hydrate missing detail payloads even when the snapshot fingerprint is unchanged.
• Hardened restored stash expansion and cached stash details so stash@{n} renumbering after stash create/drop operations does not show details for the wrong stash.
• Hardened native Version Control navigation and state so diff routes remain workspace overlays, each cwd fetches automatically only once per mounted route, stash detail identity survives positional-ref renumbering, and remote rows bind only to locals tracking the exact remote-qualified ref.
• Hardened native Version Control publishing and detail loading so repositories with multiple remotes prompt for the destination, interrupted detail requests retry without surfacing cancellation errors, and interrupted diff reads cannot remain stuck on the loading screen.
• Isolated selected-file commit preparation, message generation, and commit execution through a temporary selected-only Git index across root web, sibling-worktree web, and mobile flows; shared staging and unstaging use literal-pathspec semantics, and selected paths synchronize into the real index only after success, so failures leave the user's staged state untouched while deselected staged changes remain staged. Post-commit index cleanup is best-effort so a cleanup failure cannot report that an already-created commit failed or suppress the caller's refresh.
• Limited idle Git and filesystem churn with subscription-scoped watcher lifetimes, ignored-path suppression, focus/visibility refreshes, and a five-minute remote fetch interval.
• Extended shared RPC, IPC, Git, settings, client-runtime, and VCS contracts for the source-control snapshot and operation protocol.
• Added desktop and web context-menu separator support so destructive source-control actions remain grouped consistently after both automatic and explicit separators.
• Hardened rebase ref handling with an option separator so ref names cannot be interpreted as command flags.
• Added focused tests for source-control service behavior, provider base detection, VCS broadcaster/watch behavior, source-control panel state, shared Git contracts, and client-runtime VCS action helpers.

Why

T3 Code needs a compact place to answer "what repository work needs attention now?" without forcing users into a full external Git UI. This change keeps the surface decision-oriented: commit or stash selected changes, inspect branch sync state, publish or sync branches, review stashes, and notice when a PR/MR base has moved.

The server-owned design keeps behavior consistent across clients and avoids browser-side Git execution, while the periodic fetch and local watchers keep the panel current without introducing a high-frequency polling loop.

Validation

• Focused server coverage passed for SourceControlPanelService, VCS broadcasting and Git driver behavior, provider base detection and error handling, self-hosted GitLab CLI behavior, and desktop context-menu integration.
• Focused web coverage passed for Version Control panel logic and state, thread source-control metadata handling, and right-panel surface behavior.
• Focused shared coverage passed for Git contracts/utilities and client-runtime VCS actions.
• Focused native coverage passed for Version Control request and model behavior.
• pnpm exec vp check passed with 0 errors and 9 existing warnings in unrelated web files.
• pnpm exec vp run typecheck passed.
• pnpm exec vp run lint:mobile passed its available static checks; optional SwiftLint, ktlint, and detekt checks were skipped because those tools are not installed.
• Playwright against an isolated server on 13782, web client on 5742, and disposable throwaway repository verified that an intentional selected-file commit failure surfaces through vcs.panel.commitStaged without staging either file; after removing the failing hook, the selected-only commit succeeded, included only selected.txt, left deselected.txt unstaged, and left the real index empty.
• Integrated iOS Simulator verification was not available because no T3 Code Dev client or reusable .app artifact was installed; the TypeScript-only workflow correctly avoided a native rebuild.

Proof

---

Note

High Risk
Large cross-cutting surface touching Git mutations, thread metadata, multi-provider auth, and concurrent snapshot/cache behavior across web, mobile, desktop, and server.

Overview
Adds a server-owned Version Control command center on the web right panel and a native full-screen route, wired through new panel RPCs, live VCS watchers, and shared @t3tools/shared/sourceControl sync/compare rules documented in SOURCE_CONTROL.md.

Web and thread integration mounts SourceControlPanel per environment/thread/cwd with cached UI state, Actionable vs Remotes layout, selected-file commit/stash/discard, branch/stash/remotes actions, sibling worktrees, and ChatView metadata routing with expectedBranch guards. Mobile adds VersionControl / VersionControlDiff overlay routes from Git menus, snapshot sequencing, cwd-scoped working-tree enrichment, publish-remote prompting, and model helpers covered by unit tests.

Server and providers extend SourceControlPanelService and VCS broadcasting (debounced local watches, .git/ filtering, conservative fetch cadence). GitHub/GitLab/Azure/Bitbucket gain remote-scoped change-request lookups, optional commit author avatars, and errors normalized through sourceControlProviderError / sanitizeErrorCause so panel RPCs get bounded diagnostics. Desktop context menus now honor explicit separator items and still insert a separator before the first destructive action when it leads the menu. Client runtime adds forceRefresh on atom queries for authoritative panel reads.

^{Reviewed by Cursor Bugbot for commit 73c923a. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Version Control command center panel to web and mobile apps

• Introduces a full Version Control panel surface across web (SourceControlPanel.tsx) and mobile (VersionControlRouteScreen.tsx), exposing branch sync, working-tree file changes, commit history, stash management, and file diffs.
• Adds a SourceControlPanelService on the server and wires ~30 new WebSocket RPC endpoints in ws.ts, covering staging, committing, pull/push, branch operations, remotes, and stash actions; mutating operations trigger a git status refresh.
• Extends all four source control providers (GitHub, GitLab, Azure DevOps, Bitbucket) with a getCommitAvatarUrl method and adds per-provider showCommitAuthorAvatar settings defaulting to false.
• Adds local filesystem watchers in VcsStatusBroadcaster that debounce non-.git change events and trigger status refreshes across sibling worktrees.
• Changes the default automatic git fetch interval from 30 seconds to 5 minutes.
• Risk: the fetch interval behavioral change may cause slower detection of remote updates for existing users.

^{Macroscope summarized 73c923a.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 2396601d-ee2b-406a-94ff-fe767663f12a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

Diff is too large for automated approval analysis. A human reviewer should evaluate this PR.

^{You can customize Macroscope's approvability policy. Learn more.}

[macroscopeapp]

Effect Service Conventions: one finding in DesktopBackendManager.ts. See inline comment.

^{Posted via Macroscope — Effect Service Conventions}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c990bc9. Configure here.}