---
title: "gitpulse"
description: "Read-only GitPulse control plane for agents: worktrees, collisions, ledger, provenance, and in-process code intelligence."
canonical: https://agentpluginsdirectory.com/plugins/gitpulse
last-updated: 2026-09-25
---

# gitpulse
Read-only GitPulse control plane for agents: worktrees, collisions, ledger, provenance, and in-process code intelligence.
- Slug: gitpulse
- Publisher: GitPulse Team
- Repository: https://github.com/bharathvbcr/GitPulse
- Manifest: plugins/gitpulse/plugin.json
- Version: 1.3.5
- License: MIT
- Category (editorial): other
- Skills: 2 (gitpulse-collisions, gitpulse-insights)
- MCP servers: 1 (gitpulse)
- Stars: 12
- Repository created: 2026-08-26
- Repository last pushed: 2026-09-24
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/gitpulse
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What gitpulse does, in the publisher's words

Git, code, and tasks in one local-first desktop workspace.

Review changes, follow branch history, organize tasks, and inspect repository health from a native Rust / Tauri 2 app with a Svelte 5 frontend.

- Install GitPulse and Git for your platform.
- Open a repository and review Trust and Open. Trust allows its hooks, helpers, and project tools to run with your account permissions.
- Use Work for changes in flight, History to review a commit, and Code to explore files. Open the command palette with ⌘K / Ctrl+K.
- 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.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/bharathvbcr/GitPulse/HEAD/README.md

## Skills

- gitpulse-collisions: Detect overlapping uncommitted edits across GitPulse worktrees and agent sessions. Use when two agents, worktrees, or checkouts might be touching the same files, before merging or continuing a parked rebase, or when the user asks who is editing what.
- gitpulse-insights: Read GitPulse repository insights over MCP: worktrees, agent sessions, uncommitted changes, overlapping dirty files, ledger verdicts, and code-graph availability. Use when an agent needs a honest snapshot of a checkout before editing, when multiple worktrees or coding agents are in flight, or when…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- gitpulse: transport: stdio; command: gitpulse-mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.