AI agents
Agent integration Partly available
The agent integration connects your coding agent to GitMaster. It is a plugin that lives in its own repository, git-master-ai, under plugins/claude-code/, and Claude Code installs it from that repository's address. The plugin's hooks report each step of a session to GitMaster, which stores it as a thread. The plugin also carries the MCP server settings and a skill for the agent, so an agent can search your earlier threads.
Supported agents#
| Agent | Name in commands |
|---|---|
| Claude Code | claude-code |
Run gitmaster harness list to see the names this version knows:
claude-code Claude CodeGitMaster never changes the agent's settings files by itself: the agent's own claude plugin commands add and remove the plugin.
What the plugin contains#
| Part | What it does |
|---|---|
| Hooks | Run gitmaster thread hook when a session starts, when you send a prompt, before an edit tool runs (Edit, MultiEdit, Write and NotebookEdit), after each tool call, when the agent or a sub-agent stops, and when the session ends. |
| MCP settings | Start gitmaster mcp so the agent can use the MCP tools. Each agent session starts its own server process, in the directory the session runs in. |
| Skill | Tells the agent when to use the review and thread tools, and to treat their untrusted text as data. |
The hooks and the MCP settings run gitmaster from your PATH, so the gitmaster command must be on your PATH (see Installation). The plugin never writes a file into a repository or into the app data directory.
Skills and sub-agents#
The plugin adds skills you start yourself. Each one hands its work to a sub-agent that uses the cheapest model that is good enough and only the tools the job needs: it reads through GitMaster and records one kind of result. A sub-agent has no shell, cannot edit files and cannot reach the network. The tokens it uses are yours, in your own agent session, and the skill says what it will read before it starts.
| Skill | What it does |
|---|---|
/gitmaster:summarize-thread | Reads a thread and records a short summary on it. |
/gitmaster:propose-memories | Reads threads and proposes memories with their sources. You accept them. |
/gitmaster:prepare | For a task you describe, gathers the accepted memories, the related threads and the history of the files, and returns a brief. |
/gitmaster:review | Runs reviewers on a branch and records their verdicts and findings. |
/gitmaster:tune-reviewers | Proposes better instructions for your reviewers from the project's docs and history. |
/gitmaster:dispatch | Writes a Markdown update of the agent work of a period, from your threads. |
Nothing runs by itself. The hooks only capture. They do not start a model and they do not add text to your prompts. Text an agent writes shows in the app as Agent-written.
Install the plugin#
You need the claude command and the gitmaster command on your PATH. Run these two commands in a terminal:
The first command adds the git-master-ai repository as a plugin marketplace, from its .claude-plugin/marketplace.json. The second installs the gitmaster plugin from it. The name after @ is the marketplace's name, gitmaster.
To install the plugin from a checkout of git-master-ai instead, for example to test a change to the plugin, give the path of the checkout:
The Threads page shows these commands when no thread is stored yet.
After the install, start a new agent session in a repository. The session appears on the Threads page.
Update the plugin#
The plugin has its own version, independent of GitMaster, and declares the oldest GitMaster version it works with. Run this to get a newer plugin; upgrade GitMaster first if the plugin asks for a newer version.
What the hooks do and do not do#
- They never block the agent. A hook always ends without an error, whatever happens inside it. If GitMaster fails, the agent carries on and the event may be missing from the thread.
- They are quick. A hook writes one record and exits, with no resident process. Each hook has a five-second limit set by the plugin.
- They redact first. Secrets are replaced before anything is stored. See Secrets.
- They read only. A hook looks at the repository to find where it is and which branch it is on. It does not change the repository, and it runs no text that came from the session.
- They need the repository. A session that ran outside a Git repository is not captured.
- They can catch up. GitMaster also reads the agent's own session file, so a step that a hook missed, for example while GitMaster was not running, is filled in from the file the next time a hook runs.
Import sessions you already have#
Remove the plugin#
Removing the plugin stops new capture. Threads already stored stay until you delete them.
See also#
- Threads: read, search and delete what was captured.
- MCP server: how an agent starts the server and which tools it offers.
- Command line:
gitmaster harness listandgitmaster thread. - Installation: how to put
gitmasteron yourPATH. - Trust and safety: what the app records and where.