Skip to content
Revus
Menu

Revus 1.3.10

The Git client that keeps the why in view.

Revus is designed around the moment before a Git command: understand the repository, choose the right target, and make the move without losing the thread.

The design rule

Put the action next to the thing it changes.

history → revert · tag · cherry-pick
branch → merge · rebase · switch
conflict → resolve · continue · abort
01

Orient first.

Changes, history, branches, tags, and remotes share one readable workspace.

02

Act in context.

The next action lives beside the branch or commit it changes—not in a detached command center.

03

Recover clearly.

When Git needs attention, Revus brings the operation forward with an honest path to resolution.

Capability map

Everything you need for the next move.

No mystery roadmap badges here. This is the current product surface, written for real repository work.

01 Available

Start with context

A repository-first workspace

Open a repository and move between its changes, history, branches, and remotes without losing context.

02 Available

Know the state

Working-tree clarity

Review changed, staged, untracked, binary, and image files before deciding what to include in a commit.

03 Available

See the story

History that explains itself

Follow branches and merges in a graph, then inspect commit details, blame, file history, or the reflog in context.

04 Available

Make the next move

Actions where decisions happen

Merge, rebase, cherry-pick, revert, or create a tag from the branch or commit you are already reviewing.

05 Available

Stay in control

Recovery without hunting

When Git pauses for a conflict, see the active operation and its available continue, skip, abort, and resolution actions.

06 Available

Keep ceremony low

Remote setup, then quiet

Set up a remote or initialize a repository, then fetch, pull, push, and publish when the work calls for it.

07 Available

Stay connected

Provider-aware handoffs

Open the matching commit, repository, review, or pull request on its provider while keeping your local work in Revus.

08 Available

Go deeper

A calm surface for advanced Git

Use interactive rebase, patch workflows, external tools, and diagnostics when you need them; keep them out of the way otherwise.

09 Available

Stay in the flow

One modal language for every action

Create tags, rename branches, edit remotes, confirm recovery actions, and enter messages in focused Revus dialogs.

Built for trust

Local by default. Explicit by design.

Revus uses the native Git CLI and keeps core repository work on your machine. Online integrations are visible, optional, and provider-specific.

See what is next