Git panel

Overview

The Git tab shows source-control status for whichever workspace is currently open: what's changed, what's staged, and a diff view per file, with commit and push from the same panel.

How it works

Status lists every changed path with a code (staged/unstaged) next to it; click a path to load its diff. Fleet-automation churn — staging queues, heartbeat files, generated manifests that change constantly but rarely matter — is hidden by default behind a toggle, so real changes aren't drowned out. Committing runs the release-lane classifier when the monorepo is active, and pushing always requires an explicit confirmation rather than firing on the first click.

Steps

1. •

   Open the Git tab

   It sits alongside Browser, Terminal, Routines, Secrets, Models, and Chats.

2. •

   Check status

   See branch, ahead/behind counts, and every changed path.

3. •

   Review a diff

   Click a path to see what actually changed before you stage it.

4. •

   Stage and commit

   Stage the files you want, write a message, and commit.

5. •

   Push, deliberately

   Pushing asks for an explicit confirmation — it's never a background side effect of another action.

Capabilities

• Status + diff + stage + commit + push, all in one panel.
• Churn filtering — fleet-automation noise (staging queues, heartbeats, generated manifests) is hidden by default.
• Release-lane awareness — commits run the release-lane classifier when the monorepo is active.
• Health checks — a connections/health panel surfaces whether git and related tooling are configured correctly.

Limits & honest scope

• The panel operates on one workspace's repo at a time — it isn't a multi-repo dashboard.
• Pushing always requires confirmation by design; there's no "always push" fast path.
• It shows the repo state as reported by git — resolving merge conflicts still generally means dropping into a real terminal or editor for anything non-trivial.

Related

• Workspace layout
• Editor & file tree
• Terminal