Version 26.1 Release Candidate

SmartGit 26.1 brings a broader visual refresh. It looks more modern, uses a clearer visual language, and feels more coherent across light and dark themes.

Reworked Icon Set

The icon set has been completely reworked. It now looks more modern, uses only a few distinct colors, and comes in different variants for light and dark themes.

• Cleaner look – more modern shapes and a smaller, more deliberate color palette.
• Better contrast – dedicated light and dark variants improve recognition in both themes.

Improved Dark Theme

The dark theme has been refined further.

• Darker overall appearance – background tones are deeper and less washed out.
• Matched icon variants – the new icon set includes dedicated dark-theme versions.

Reworked Compare Colors

File Compare now uses a more familiar color language.

• Changed = yellow – modified blocks are easier to recognize at a glance.
• Added = green – added content is highlighted with the color users already expect.
• Deleted = red – removed content stands out more naturally than before.

Git is evolving toward SHA-256 object IDs and reftable refs. SmartGit 26.1 is ready for that transition.

• SHA-256 repositories – SmartGit can work with repositories using Git’s newer object format.
• Reftable support – the newer ref storage backend is supported as well.

The Standard window now includes GitLab support on par with the existing GitHub support.

• GitLab merge requests – merge requests are integrated into the Standard window workflow.
• GitLab CI in My History – CI pipeline state is shown for merge requests, branches, and diverged remotes.
• Browse in GitLab – the active branch or repository can be opened directly in GitLab from the Browse button.
• Commit messages from GitLab issues – commit messages can be created from selected GitLab issues.

Branches attached to worktrees are now shown in Branches and the Graph together with their current worktree state.

• See the current worktree state at a glance – refs show whether the linked worktree is clean or modified, and tooltips can show the related worktree path.
• Open worktree repositories stay in sync – related open worktree repositories are refreshed immediately, so Branches and the Graph stay up to date across them.
• Smoother Graph interaction – the “switch to worktree” dialog can be disabled, and clean worktree refs can be dragged in the Graph.

Commit Overlap adds a new dimension to the Graph: the Overlap column shows how strongly a commit overlaps with a selected or pinned comparison commit. This makes it easier to spot related commits, identify candidates for reordering or squashing, and notice possible upstream conflicts earlier.

• Overlap categories – SmartGit distinguishes between no overlap, slight overlap, heavy overlap, subset, superset, and same modified files.
• Tooltip details – tooltips can list common files and potential conflicts.

SmartGit’s three main windows look similar enough that it is easy to open the wrong one and wonder why the UI suddenly feels so different. It was not always obvious at a glance which main window was currently open or how to get to the other ones.

Each window now has its own identity through easy-to-recognize, easy-to-distinguish icons. SmartGit 26.1 also makes the current window easier to recognize and the other two easier to discover from the top-right corner, giving you clearer orientation, noticeably less confusion, and easier switching if you did open the wrong one.

SmartGit 26.1 extends the AI workflow in three important ways.

• Ask AI with custom prompts – run Ask AI with a user-defined prompt on multiple selected commits at once, for example as a final sanity check of a feature branch.
• More flexible prompt templates – commit message generation, rewording, and Ask AI support the {{ branch }} placeholder. Templates can use @ai-marker, and only that marker is replaced by the LLM response.
• Merge commits and signed commits – Ask AI now works for merge commits, and AI rewording preserves signatures of signed commits.

Working with multiple provider accounts is now more transparent in the Standard and Log windows.

• Switch explicitly – select the active provider configuration directly in the UI, so it is clear which account or site is currently in use.
• Per-remote selection – provider configurations can also be selected on remotes.

Multi-remote repositories now make Pull behavior clearer.

• Choose the default directly – set whether Pull uses the current remote or all remotes from the toolbar popup.
• More control after fetch – deleting merged branches after Pull is now optional.