Skip to main content
plugin

kauri — Claude Code plugin: decisions and setup

kauri brings project decisions into Claude Code sessions, lets the agent record and query them, and flags stale records after commits.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-plugins-community
/plugin install kauri@claude-community
Open on GitHub

What kauri does

kauri keeps decision records available during Claude Code work. A startup hook adds the pinned records and index to the session context, then restores that projection after compaction. Another hook checks for stale records after git commit.

The plugin starts kauri serve as an MCP server and exposes 12 tools for recording, updating, querying, viewing, validating, and checking decisions. It also includes /kauri:record-decision [title] and /kauri:check-staleness. Records can use project-level or user-level scope. The kauri binary must be on PATH, and the project needs an initialized store from kauri init.

What it helps with

  • bring project decisions into each new coding session
  • record an architecture choice with a guided command
  • query and inspect saved decisions
  • catch stale records after git commit

Example prompts for the agent

  • Record the decision to use a library for authentication with the title “Authentication library choice”.
  • Check which decisions became stale after the latest commit.
  • Show the history for the API structure decision.

How to install kauri

Plugin marketplace

/plugin marketplace add anthropics/claude-plugins-community
/plugin install kauri@claude-community

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about kauri

How do I install kauri in Claude Code?

Add the marketplace with /plugin marketplace add anthropics/claude-plugins-community, then install the plugin with /plugin install kauri@claude-community.

What does kauri do?

It puts Kauri decision records into Claude Code context, exposes MCP tools for working with them, and checks for stale records after git commit.

What does kauri need before it can run?

The kauri binary must be available on PATH, and the project store must be initialized with kauri init. The plugin provides the recording and staleness-check commands.

Source text

claude-code · MIT
# Kauri Plugin for Claude Code

Integrates [Kauri](../../README.md) with Claude Code so that project decisions
are visible in every coding session and the agent can record, query, and
validate decisions as first-class MCP tools.

## What it does

| Feature                   | How                                                                                                  |
| ------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Decisions in context**  | Session-start hook injects the Kauri projection (pinned + index) into Claude's context automatically |
| **MCP tools**             | Claude sees `kauri_record`, `kauri_query`, `kauri_show`, etc. alongside Bash/Read/Edit               |
| **Skills**                | `/kauri:record-decision` and `/kauri:check-staleness` teach Claude when and how to use Kauri         |
| **Post-commit staleness** | After `git commit`, a hook checks for stale decisions and alerts Claude                              |

## Prerequisites

- [Claude Code](https://claude.ai/code) installed
- `kauri` binary in PATH (`brew install kauri` or download from [Releases](https://github.com/mhashim6/kauri/releases))
- A Kauri store initialised in your project (`kauri init`)

## Installation

### From the Kauri marketplace

```bash
# Add the marketplace (one-time)
/plugin marketplace add mhashim6/kauri

# Install the plugin
/plugin install kauri@kauri
```

### MCP server only (any MCP client)

If you only need the 12 MCP tools without hooks and skills:

```bash
# Claude Code
claude mcp add kauri -- kauri serve
```

For other MCP clients (Cursor, Windsurf, Claude Desktop), add to your config:

```json
{
  "mcpServers": {
    "kauri": { "command": "kauri", "args": ["serve"] }
  }
}
```

### From local source (for development)

```bash
claude --plugin-dir ./plugins/claude-code
```

Or reload during a session:

```
/reload-plugins
```

## What gets registered

### MCP Server

The plugin registers `kauri serve` as an MCP server. Claude Code starts it
automatically and exposes all 12 Kauri tools:

`kauri_record` `kauri_update` `kauri_query` `kauri_show` `kauri_history`
`kauri_validate` `kauri_project` `kauri_pin` `kauri_unpin`
`kauri_taxonomy_list` `kauri_taxonomy_add` `kauri_check`

### Hooks

| Event                    | Trigger              | Action                                                |
| ------------------------ | -------------------- | ----------------------------------------------------- |
| `SessionStart` (startup) | New session begins   | Injects decision projection into context              |
| `SessionStart` (compact) | Context is compacted | Re-injects projection so decisions survive compaction |
| `PostToolUse` (Bash)     | After a `git commit` | Runs staleness check, alerts if records are stale     |

### Skills

| Skill           | Invocation                       | Purpose                                      |
| --------------- | -------------------------------- | -------------------------------------------- |
| record-decision | `/kauri:record-decision [title]` | Guided workflow for recording a new decision |
| check-staleness | `/kauri:check-staleness`         | Review and resolve stale decisions           |

## Troubleshooting

**"kauri: command not found"** — The `kauri` binary isn't in PATH. Either:

- Run `bun run build` in the Kauri repo and add `dist/` to your PATH
- Or use `bun run /path/to/kauri/src/cli.ts` and update `.mcp.json` accordingly

**No decisions showing at session start** — Make sure you've run `kauri init`
in your project directory and have at least one recorded decision.

**MCP tools not appearing** — Check that the plugin is loaded:

```
/reload-plugins
```

Then verify with `/kauri:check-staleness` — if the skill loads, the plugin is active.

© mhashim6 · MIT · mhashim6/kauri

Similar plugins

All plugins for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor