Overview Section
Overview is the default section the panel lands on when you open it, and the one you will return to most often during a normal workday. It is a single scrollable column of small cards that together answer the question "what is the state of this repository right now, and what should I do next?"without having to click around.
Suggestions
The top card is a short, ranked list of up to three Suggestions. Each suggestion is a single line of plain English describing the most actionable thing about the current state, and most of them come with an inline button that jumps you to the right place (for example Go to Changes or Go to Settings). Suggestions disappear as the underlying condition is resolved — fix a conflict and the conflict suggestion vanishes on the next refresh.
The list is drawn from nine possible states, sorted by priority and capped at three. Only states that currently apply show up. The full set is:
- •Conflicts to resolve: "N file(s) have conflicts — resolve them" with a Go to Changes button. Highest priority.
- •Merge in progress: "Merge in progress — resolve conflicts and commit" with a Go to Changes button.
- •Rebase in progress: "Rebase in progress" with a Go to Changes button.
- •Diverged (ahead and behind): "Both local (N) and remote (M) have changes — pull first" with a Go to Changes button. This takes priority over the single-direction suggestions below.
- •Behind remote: "N new commit(s) on remote — pull to update". Shown only when you are behind and not also ahead.
- •Ahead of remote: "N commit(s) ready to push". Shown only when you are ahead and not also behind.
- •Unstaged or untracked changes: "N file(s) changed — stage and commit" with a Go to Changes button.
- •Staged, nothing else: "Files staged — ready to commit" with a Go to Changes button. Shown when you have staged files and no other pending changes.
- •No remote configured: "No remote configured — add one in Settings" with a Go to Settings button.
- •Everything clean: "Everything up to date — no changes". Shown only when the working tree is clean, the branch is in sync with its remote, and no merge or rebase is in progress. No action button.
When there is nothing to suggest (which can happen briefly while data is still loading), the Suggestions card is hidden altogether rather than showing an empty box.
Repo Status
Below Suggestions sits the Repo Status card — a compact two-column summary of the repository at this instant. Every field is derived from live data and refreshes automatically when the working tree changes or a remote operation completes.
- •Branch: the currently checked-out local branch name.
- •Remote: the upstream this branch is tracking (for example origin/main), or none if the branch has no upstream.
- •Last: how long ago the most recent commit was made, shown as a relative time (just now, 12m ago, 3h ago, 2d ago, 1w ago).
- •Author: the name recorded on the most recent commit.
- •Most recent commit message: the first line of the latest commit in quotes, followed by its short hash prefixed with # (for example "Initial commit" #abc1234). Spans both columns.
- •Sync indicator: a colored dot with a text label. It reads Synced when the branch is in sync with its upstream, or a summary such as 2 ahead, 3 behind, or 2 ahead, 3 behind otherwise.
- •Special-state badges: next to the sync indicator the card can show a MERGING or REBASING pill when a merge or rebase is mid-flight. These disappear as soon as the operation finalizes or is aborted.
Quick Stats
A single-line card listing three counters at a glance. It is the fastest way to see whether there is anything to commit without opening the Changes section:
- •Modified: number of tracked files whose working-copy content differs from the last commit and that have not been staged yet.
- •Untracked: number of files present in the folder that are not under Git's control yet (new flow files, new specs, etc.).
- •Staged: number of files currently on the index, waiting for the next commit.
These three counters also drive the badges shown next to the Changesentry in the section navigation on the left.
Recent Commits
A miniature commit log showing the five most recent commits. Each row has the short hash, the first line of the commit message (truncated if it is long), and a short relative time on the right (for example 2h, 3d, 1w). If the repository has no commits yet, the card shows a friendly "No commits yet" placeholder instead of an empty list.
This list is purely informational — it is a quick glance at what just happened. For search, filtering, full commit details, and per-commit diffs, move to the History section (covered later in this chapter).
Quick Actions
The final card on the Overview section is a row of three shortcut buttons that take you directly into the most common follow-up tasks:
- •Commit: switches the panel into Commit Mode (same as clicking Commit in the toolbar). Use it when Repo Status or Quick Stats told you there is something to stage.
- •New Branch: jumps to the Branches section (which is where branch creation, via the New Branch dialog, actually lives).
- •Stash: jumps to the Stashes section so you can park work-in-progress before switching branches or pulling in new commits.
None of these buttons perform an operation on their own — they are pure navigation shortcuts. Nothing on the Overview section ever changes the repository state on its own; every destructive action requires you to move to the relevant section and confirm there.