GitPulse

Fast, local-first Git desktop client, code intelligence suite, and task workspace.

Review changes with GPU acceleration, resolve 3-way conflicts, follow branch and commit
history, search across repositories, organize tasks with board swimlanes, and inspect repository
health from a native Rust / Tauri 2 app with a Svelte 5 frontend. 100% on-device, private-by-design,
zero telemetry.

Download ·
Getting started ·
Documentation ·
Website ·
Release notes

Get started

1. Install GitPulse and Git for your platform.
2. Open a repository and review Trust and Open. Trust allows its hooks,
   helpers, and project tools to run with your account permissions.
3. Use Work for changes in flight, History to review a commit, and
   Code to explore files. Open the command palette with ⌘K / Ctrl+K.
4. Replay the guided tour any time from Settings → Appearance → Guided walkthrough.

GitHub CLI, DevMap, Manvi, and local model servers are optional; install the
ones needed for the features you use. The first repository guide
walks through a review, task creation, and optional setup.

Four views, one workspace

GitPulse has 4 application views with 18 specialized sections. Each view keeps related sections together.

Graph, Diff and Suspects share the selected commit; Explorer and Blame share the selected
file; Overview embeds branch stack hierarchy. Fleet compares repositories across the workspace (scaling to 1,000 repositories with 24 active watches),
Tasks opens global and saved-workspace boards with swimlanes and WIP limits, and the terminal dock stays available across views.

From a change to the next step

• Review and commit. Canvas commit graph (100K+ commits at 60/120 FPS), unified and side-by-side diffs,
  word highlighting, symbol-grouped diff hunks, image comparisons, selective staging,
  stash previews, a three-way conflict resolver, and structured patch-brief commit
  phrasing with on-device Apple Intelligence fallback.
• Manage worktrees and branches. Dead-branch cleanup with durable tip backups
  in the WAL ledger and authorized delete commands, copy-on-write build cache sync
  (node_modules, target, .venv), named localhost routes via portless, and
  trust-gated lifecycle hooks.
• Organize the work. Quick add parses priority, labels, owner, repository,
  due date, and notes. Board views with swimlanes (grouped by owner or label),
  saved views, column WIP limits, task checklists with done states, cross-task links
  (parent, blocks, related, duplicate), the Archive dock with Deleted recovery,
  review drafting suggestions, and agent terminal handoff with per-launch model selection.
• Explore and search the code. File navigation and blame are built in. High-speed
  repository-wide text search (git grep over working tree or revisions with honest
  cancellation and truncation reporting). Add DevMap for structural navigation,
  symbol search, symbol-level collision detection, dependencies, impact, and candidate tests.
• Inspect the repository. Universal coverage reports across 6 formats (LCOV, Cobertura,
  Go cover, Istanbul, JaCoCo, Clover), multi-ecosystem dependency audits (cargo-audit,
  npm audit, pip-audit, govulncheck) with cargo deny and cargo crev parsers,
  Kingfisher redacted secrets scanning that locates each finding against Git, storage
  cleanup previews, and Pulse activity summaries distinguish results from scans that did not run.
  Capped results identify their limits.
• Work from the desktop. Native menus, a command palette (⌘K), a docked PTY terminal
  that reports what each session is running, reflog recovery (reset --keep), GitHub pull
  request actions (review, comment, approve, merge pinned to viewed commit), colour-coded repository
  tabs and groups that survive a restart, and an optional macOS menu-bar status popover keep
  frequent actions close. Background windows stop their timers instead of polling.

The feature reference describes each surface and its limits.
The changelog records release changes; open qualification
tracks remaining platform, provider, and performance checks.

File explorer	Diff review
Coverage	Dependency health

Screenshots are captures from the macOS app; appearance varies by release and platform.

Local state and explicit permissions

Repository and task state are stored locally. The desktop app has no remote
telemetry. Git remotes, GitHub operations, Firebase App Hosting checks you ask for,
optional tool downloads, release checks, and configured agent providers can use the
network.

Built-in local AI connects to loopback model servers. Task enhancement and agent
runs use their configured provider; supported Mac builds can also use Apple
Intelligence for task titles and descriptions. These are distinct execution paths.

Repository trust is an execution decision. A worktree is not an OS sandbox.
Policy verdicts preserve unchecked separately from allowed, and the
read-only MCP server cannot grant repository trust. Read the
security and trust model before configuring agents.

Architecture

DevCouncil is components and modules. Manvi wraps them. GitPulse uses Manvi
for policy, workbench, and agent hosting, and selected DevCouncil components
for code intelligence. Modules can be updated independently.

flowchart TB
    subgraph Frontend["Svelte 5 Frontend (Runes & TS)"]
        direction LR
        Views["4 Views · 18 Sections<br/>(Work, Code, History, Insights)"]
        Canvas["GPU HTML5 Canvas<br/>Commit Graph"]
        TerminalDock["PTY Terminal Dock<br/>(portable-pty)"]
    end

    subgraph IPC["Tauri 2 IPC Seam"]
        Bridge["invoke('cmd_*') — 288 Handlers<br/>Zero-Drift Pre-Commit & CI Contracts"]
    end

    subgraph Backend["Rust Backend (Tauri 2 / Rayon)"]
        direction TB
        GitEngine["Git Sandbox & CLI Reader"]
        LaneSolver["Topological Lane Solver"]
        Analyzers["Coverage, Health & LOC"]
        Ledger["Durable WAL Event Ledger"]
        Headless["Headless Binaries<br/>(gitpulse-mcp · gitpulsed · gitpulse-hook)"]
    end

    subgraph Integrations["Modular Integrations & Local Tools"]
        direction TB
        subgraph ManviWrap["Manvi (Wraps DevCouncil Modules)"]
            ManviSidecar["manvi serve --posture host<br/>(5-verdict policy gate & workbench DB)"]
        end
        subgraph DevCouncilMods["DevCouncil & DevMap"]
            Vendored["Vendored Readers<br/>(devmap-store, devmap-query, dc-store)"]
            DevMapCLI["devmap CLI & daemon socket<br/>(build --manifest, search, impact)"]
        end
        subgraph LocalTools["Local Machine"]
            CLI["git & gh CLI"]
            LocalLLM["Loopback-Only LLMs<br/>(Ollama / LM Studio)"]
        end
    end

    Frontend --> Bridge
    Bridge --> Backend
    Backend --> ManviWrap
    Backend --> DevCouncilMods
    Backend --> LocalTools

See architecture for ownership and contracts, and
module integration for the boundaries between projects.
GitPulse succeeds the deprecated LiquiTask
workbench; this does not imply complete feature parity.

Build and contribute

Use Bun 1.4.2, Node.js 22.x (22.12 or newer), stable Rust, Git, and your platform's native
build tools. The contributor guide covers setup and platform prerequisites.

git clone https://github.com/bharathvbcr/GitPulse.git
cd GitPulse
bun install --frozen-lockfile
git config core.hooksPath .githooks
bun run tauri dev

The browser regressions run twice in CI — under Chrome on Linux and under
WKWebView on macOS — because the two engines disagree often enough to matter: a
fixture can pass under one and fail under the other. ci:local runs both for
that reason, so prefer it over the individual commands before opening a pull
request.

A frontend build alone does not qualify the native application. Follow the
release procedure before publishing a build.

Documentation

The documentation index organizes user guides, integration
references, contributor contracts, and historical evidence. Start with
installation, your first repository,
or tasks and workspaces.

Bug reports, documentation, design, tests, and code contributions are welcome.
See CONTRIBUTING.md and good first issues.

Getting help

Questions and open-ended proposals go to
Discussions — ask in
Q&A, where an answer can be marked accepted, or start in Ideas. Bugs,
scoped feature requests, and adapter proposals go through
issues, which has a
template for each. Suspected vulnerabilities are the exception: report those
through GitHub Security Advisories as described in the
security and trust model, not as a public issue.

The bug template asks for a diagnostics report: open the command palette and
run Open Diagnostics, then use its copy button, which collects the version,
platform, and recent log lines. Read it before pasting — it can contain
repository paths.

Contributors

Every kind of contribution is recognised here, not only code — documentation,
design, bug reports, testing, reviews, and ideas all count under the
all-contributors
specification. The list below is generated from .all-contributorsrc.

To add someone (including yourself), comment on any issue or pull request:

@all-contributors please add @username for code, doc

The bot opens a pull request updating this section and .all-contributorsrc.
See the emoji key for contribution
types.

Topics, Tags & Discoverability

License

Distributed under the MIT License. See LICENSE for details.

© 2026 Bharath Chandra Vaddaram