Claude Code

Install the Baz plugin in Claude Code.

The Baz plugin for Claude Code adds indexed cross-repository search, the codebase-exploration skill, and two commands: /baz:plan-with-baz and /baz:review.

Install

/plugin marketplace add baz-scm/baz-plugin
/plugin add baz
/reload-plugins

Claude Code reads the plugin manifest, loads the baz-codebase-exploration skill, registers the Baz MCP server, and wires the session hooks. The first time the agent calls a Baz tool your browser opens for OAuth, and you sign in with your Baz account.

To confirm the server is connected, run /mcp and look for baz in the list.

What gets wired

Piece	Effect
MCP server `baz`	`repo_search`, `remote_grep`, and `remote_file_search` become available as `mcp__baz__*` tools.
`baz-codebase-exploration` skill	Auto-loads when you ask Claude to plan, scope, or investigate a change. Routes searching through Baz and reading through Claude’s own tools.
`/baz:plan-with-baz` command	Manually invoked planning workflow.
`/baz:review` command	Diff-scoped code review with cross-repository checks. Also triggers on plain requests such as “review my changes”.
Session hooks	`SessionStart` passes your session id and current repository to the agent, `PostToolUse` records Baz tool calls, and `SessionEnd` prints a per-session tool usage summary.

Planning with Baz

Run the command with a short description of the work:

/baz:plan-with-baz add rate limiting to the public API

Claude enters plan mode (you confirm with one click), explores the relevant repositories with the Baz tools, including repositories you have not checked out, and produces a structured implementation plan. Nothing is written until you approve.

When planning finishes, Claude calls update_plan, which stores the plan in Baz and closes the planning session on your timeline. See Planner for the plan record itself.

Reviewing with Baz

Review the current branch, or narrow the scope with a flag:

/baz:review
/baz:review uncommitted
/baz:review --pr 42
/baz:review --fix

Claude resolves the diff, reads the changed files, then spends the Baz search budget checking the change against repositories you have not cloned. Asking in plain language works too, since the review skill is model-invocable: “review my changes before I push” reaches the same workflow.

If the Baz server is not connected, run /mcp to check its state. For a change with an outward-facing surface, the review stops rather than quietly downgrading to a local-only pass. The full scope flags, the four cross-repo checks, and the --fix loop are described in the plugins overview.

Connecting the MCP server without the plugin

If you only want the search tools and not the skill, hooks, or planning command:

claude mcp add --transport http baz https://baz.co/mcp

Troubleshooting

Tools are missing after install. Run /reload-plugins, then /mcp to check the server state.
Auth loops. Clear the stored MCP credentials with rm -rf ~/.mcp-auth and restart Claude Code.
Claude greps locally instead of using Baz. The skill loads on planning-shaped requests. If a request does not look like planning, name the Baz tools explicitly or run /baz:plan-with-baz.

More detail on the shared pieces is in the plugins overview.