Git in the editor
Stage, commit, fetch and push without leaving the terminal — and a diff viewer that reads like the tool you already use.
Git panel
The git panel in FigyTerm's editor with changed files ticked for staging and a commit summary typed
public/screenshots/git-panel.pngTick, summarise, commit
File-level staging in a panel shaped like GitHub Desktop's. Tick what belongs in the commit, write the summary, commit.
A diff you can read
Unified or split, with word-level highlighting inside changed lines, and five presets so it looks like the diff tool you already know.
Your git, not a reimplementation
It shells out to the git on your PATH, so your hooks, your config and your credential helper all apply exactly as they do on the command line.
Status where you are already looking
Changed files are badged in the file tree and changed lines are marked in the gutter, so the state of the working tree is visible while you edit rather than something you stop to ask for. The status bar carries the current branch.
Git panel
The git panel in FigyTerm's editor with changed files ticked for staging and a commit summary typed
public/screenshots/git-panel.pngA diff viewer with five faces
Everyone has a diff they read fastest. Rather than pick one, the viewer ships presets for GitHub, GitLab, VS Code, delta and plain `git diff`, in unified or split layout, with word-level highlighting inside changed lines so a renamed variable does not look like a rewritten paragraph.
Diff viewer
FigyTerm's split diff viewer with word-level highlighting inside the changed lines
public/screenshots/diff-viewer.pngHistory, and the two remote operations worth having
A history tab lists commits; opening one slides out a drawer with its message and the files it touched. Fetch and push are there. Discards go to the system trash rather than into nothing.
- Built
- Tree decorations, gutter marks, branch indicator, file-level staging, commit, history drawer, fetch, push.
- Not built
- Hunk-level staging, branch switching and pull. Those stay on the command line, where you already have them.
Commit history
The commit history tab in FigyTerm's editor with a commit opened into a drawer listing its files
public/screenshots/git-history.pngFAQ
Git & diffs, in short
Does it use my git configuration?
Yes. FigyTerm runs the git on your PATH rather than reimplementing it, so your hooks, aliases, signing configuration and credential helper all apply.
Can I stage individual hunks?
Not yet — staging is file-level. Hunk-level staging, branch switching and pull are deliberately left to the command line for now.
What happens to a discarded change?
The file goes to the system trash, not to nowhere. A discard you regret is recoverable.
Keep reading
Related features
Give your terminal its whole workbench
Free, MIT licensed, and entirely local. On macOS one command does it; Linux and Windows are one download away.
curl -fsSL https://raw.githubusercontent.com/code4mk/figyterm/main/install.sh | sh