Status and sync at a glance
The header shows your branch, its upstream, and what is waiting to pull or push. Fetch, Pull, Push, and Merge main are one click away, with Force Push (Safe) using force-with-lease.
A full Git client in Flame IDE: fetch, pull, push, merge main, a commit graph with diffs, branches, tags, stashes, squash, worktrees, submodules and compare.
Most Git work is small and frequent: check what is waiting to pull, look at a commit, compare a branch, stash something, squash two fixups. A separate Git GUI turns each of those into a context switch. Flame's Git panel keeps the repository beside the editor, with the same diffs, language navigation, and AI tools you use for code, across every project in your workspace.
The header shows your branch, its upstream, and what is waiting to pull or push. Fetch, Pull, Push, and Merge main are one click away, with Force Push (Safe) using force-with-lease.
Search commits by message, author, or hash, open a commit's full details, and view its diff in the editor. Arrow through commits with the keyboard to preview each one, or pop the commit graph out into a full tab.
Local and remote branches sit side by side, with a Merged badge when a branch is already in the default branch. Tags list every release. Stashes can be applied, popped, dropped, or turned into a branch.
Squash recent commits and edit the message before anything is rewritten. Interactive rebase, cherry-pick, revert, reset, undo last commit, and Git notes are in the commit menu.
Open the Git panel from the left activity bar. It follows the current project, or the worktree you have open, so the actions always apply to the checkout you are looking at.
The toolbar shows ahead and behind counts against the upstream. Pull and merge the default branch into a feature branch in one step, or pull it directly when you are on it.
Force Push (Safe) refuses to overwrite commits on the remote that you have not seen. Saved custom push commands, such as a GitLab merge request with push options, run from the same menu.
From the Projects panel, Update projects pulls fast-forward changes in every filtered repository and Switch to default branch moves them all to main. Projects with local changes or diverged history are skipped, never stashed or forced.
Commits show as compact cards. Select one to expand its subject, description, author, date, and refs, and to open its diff against its first parent in the editor.
Open Git Graph as an editor tab to see branch topology, tags, and merges. Pick any commit to see the files it changed and the full diff beside it, with Blame, Split, and Inline views.
Compare branches, tags, or commits in a full side-by-side diff. Go to Definition, references, and hovers work in both panes through the file's language server, even against remote branches like origin/main.
Move through commits with the arrow keys to preview each diff, press Enter to fold or open a card, and Escape to collapse it or clear a search.
Running several branches at once is a first-class workflow in Flame, for you and for AI agents.
Open a branch in its own worktree or create a new one, optionally bringing your uncommitted changes. Bring a worktree's changes into your branch without a commit, and prune stale entries when a folder was deleted.
Submodules get their own tab with update and sync built in, so a nested dependency does not require a separate tool.
Switch projects from the right side and the Git panel follows. Branch status for every repository is visible in the Projects panel, so you can see which ones need a pull before you open them.
Branch and upstream status, one-click Fetch, Pull, Push and Merge main, safe force push, squashing, searchable history, a full-tab commit graph, branch, tag and stash cards, worktrees, submodules, and side-by-side revision comparison.
Open the Git panel and read the header: branch, upstream, and commits waiting to pull or push. Fetch if you need the latest remote state.
Search commits or open Git Graph in a tab. Select a commit to read its message and its diff, or compare two branches side by side.
Squash fixup commits into one and edit the message, or stash unfinished work. Use a worktree when a second branch needs its own checkout.
Merge the default branch into your branch, resolve any conflicts in the three-way editor, then push or run a saved custom push command.