This page tells you how to add the dotclaude marketplace and install each plugin. It is for users who run Claude Code and want dotclaude. Read it before Quickstart.

The core plugin is dotclaude. dotclaude-codegraph, dotclaude-browser, dotclaude-docs, dotclaude-sessions, and dotclaude-lab are optional add-ons. Each add-on works without the core plugin. The second_opinion tool is part of the core plugin.

The commands on this page are for Claude Code 2.1.296. That is the minimum version, from TESTED_VERSION in src/plugins/dotclaude/slices/setup/domain/facts.ts.

Check that each tool in the table is ready for the plugins that you install.

The checks of the core hooks module need no Bun and no Node.js, because the core plugin loads them as a hooks module. The core plugin's hooks.json names only register.ts.

On a machine with managed settings, or with a Team or Enterprise login, Claude Code loads the built-in guard sec-default. A user cannot disable it. In a measurement on Claude Code 2.1.292, the guard bypassed the prompt.section hook of dotclaude. The context_management text did not reach the prompt. The tool.check hook and the classic PreToolUse hook still ran. See Request build.

1. Add the marketplace.

   /plugin marketplace add xsyetopz/dotclaude
   

2. Install the plugin.

   /plugin install dotclaude@dotclaude
   

3. Apply the settings snippet with the setup skill, then restart Claude Code.

   /dotclaude:setup
   

A plugin cannot set permissions, environment variables, or models. Claude Code applies only agent and subagentStatusLine from a plugin settings file. Without the settings snippet, compaction stays on, the full system prompt stays, and the status line, the permission rules, and the sandbox are not set.

The setup skill previews each change first. It writes nothing until you say yes. The skill runs this command for the scope that you choose:

dotclaude-setup settings --scope user --apply

The scopes are user (~/.claude/settings.json, the default), project (.claude/settings.json), and local (.claude/settings.local.json). When CLAUDE_CONFIG_DIR is set, the command uses that folder in place of ~/.claude. Run /dotclaude:setup again after each update of the plugin, because the status line commands hold the path of the plugin version. The merge adds the keys and rules of the snippet. It keeps your other keys, except availableModels, which it replaces. See Settings snippet for the keys. See Settings snippet keys for the reason of each key.

After the settings step, the setup skill checks the tools of each installed add-on. The check reads the codegraph CLI and its index, agent-browser, npx, and the Bun version. The check reads npx, not bunx, although the docs skill of dotclaude-docs runs ctx7 through bunx (see the table above). The setup skill installs a missing CLI only after you say yes. The project step codegraph init -y runs only with dotclaude-setup addons --apply.

The second_opinion tool is part of the core plugin, so it needs no separate install. To use TypeSafe Jev, export the key before Claude Code begins.

export TYPESAFE_API_KEY=<your key>

Each call sends the question, the options, and the state of the decision to the TypeSafe API. Without a key, or when Jev gives no answer, a small Claude model answers. See Second opinion.

1. Install the plugin.

   /plugin install dotclaude-codegraph@dotclaude
   

2. Install the CLI.

   bun i -g @colbymchenry/codegraph

3. Build the index once in the project.

   codegraph init -y

The plugin works only in a project that has an index. The plugin does not change the telemetry setting of the CLI. See Code graph.

/plugin install dotclaude-browser@dotclaude

The plugin loads the browse skill. It also replaces the built-in WebSearch with a search in the headless browser. It uses agent-browser by default. To run agent-browser with the CloakBrowser binary on sites with bot detection, set the backend option to cloakbrowser. Run /plugin configure dotclaude-browser to set the option. See Browser.

/plugin install dotclaude-docs@dotclaude
/plugin install dotclaude-sessions@dotclaude
/plugin install dotclaude-lab@dotclaude

dotclaude-docs adds the docs skill, which gets current library docs through ctx7. See Library docs. dotclaude-sessions adds the bins dotclaude-start and dotclaude-usage, and the skills start-cost and usage. See Sessions. dotclaude-lab adds the tools for plugin authors. See Lab. None of the three needs a key. The docs skill uses CONTEXT7_API_KEY only to raise the quota limit.

1. Update the marketplace and the plugins.

   claude plugin marketplace update dotclaude
   claude plugin update dotclaude@dotclaude

   For each add-on that you installed, run one more claude plugin update command. Replace dotclaude with the name of the add-on:

   claude plugin update dotclaude-codegraph@dotclaude
   claude plugin update dotclaude-browser@dotclaude
   claude plugin update dotclaude-docs@dotclaude
   claude plugin update dotclaude-sessions@dotclaude
   claude plugin update dotclaude-lab@dotclaude

2. Restart Claude Code. The help of claude plugin update says that a restart applies the update.

3. Read the new entry in the CHANGELOG.

4. Run /dotclaude:setup again. The status line commands hold the path of the plugin version, so each update needs a new run. The drift check reports the differences that remain when a session begins.

1. Uninstall each add-on that you installed.

   claude plugin uninstall dotclaude-codegraph@dotclaude
   claude plugin uninstall dotclaude-browser@dotclaude
   claude plugin uninstall dotclaude-docs@dotclaude
   claude plugin uninstall dotclaude-sessions@dotclaude
   claude plugin uninstall dotclaude-lab@dotclaude

2. Uninstall the core plugin, then remove the marketplace.

   claude plugin uninstall dotclaude@dotclaude
   claude plugin marketplace remove dotclaude

3. Remove the keys of the settings snippet by hand. The setup command does not remove them. Remove the statusLine and subagentStatusLine keys first. These keys hold the path of the plugin folder. See Settings snippet.

Claude Code 2.1.296 has the --plugin-dir <path> flag. The flag loads a plugin folder for one session.

claude --plugin-dir /path/to/dotclaude/plugins/dotclaude

For a separate config, see Sandbox.

• Quickstart: see what happens in a first session.
• Troubleshooting: find the fix for a symptom.
• Architecture: see each part of the core plugin.