Install

Install

Install the dotclaude marketplace, then each plugin that you want. The core plugin is dotclaude. dotclaude-browser, dotclaude-jev, and dotclaude-modder are optional.

Before you begin

Need	For	Note
Claude Code 2.1.292 or later	all plugins
git	dotclaude
Node.js 22.18 or later on PATH	the setup script, the status line, and the auto-mode guard of dotclaude, the script of dotclaude-jev, and OpenSpec	Without Node.js, the auto-mode guard does not run, and the auto-mode classifier decides the calls.
gh on PATH	the policy ask of dotclaude	Without gh, the ask does not run and the call goes on.
TYPESAFE_API_KEY	dotclaude-jev	Export it before Claude Code starts.
Bun 1.4.2 or later on PATH	the um command of dotclaude-modder	Only for the modder.

The core hooks module needs no Node.js, because Claude Code runs it. The um command stays on Bun, because the field notes need a YAML parser, and Node.js has none built in.

On a machine with managed settings, or with a Team or Enterprise login, the built-in guard sec-default loads. It skips the prompt.section hook of dotclaude, so the context_management text of dotclaude does not load. The other parts work. See Claude mods.

Install the core plugin

1. Add the marketplace.

   /plugin marketplace add xsyetopz/dotclaude
   

2. Install the plugin.

   /plugin install dotclaude@dotclaude
   

3. Run the setup skill, and restart Claude Code.

   /dotclaude:setup
   

A plugin cannot set permissions, environment variables, or models. The setup skill merges one profile into a settings file that you choose. It shows each change and makes a backup first. It keeps the 3 newest backups. It also sets the status line. The skill offers to install OpenSpec, and it prints the sudo command for the managed settings but never runs it. See OpenSpec and Guards.

Install the browser plugin

/plugin install dotclaude-browser@dotclaude

The plugin loads the drive-web-browser skill and has no hooks. It uses agent-browser by default. Set its backend option to cloakbrowser to run agent-browser with the CloakBrowser binary on sites with bot detection. See Browser.

Install the Jev plugin

1. Export the key before Claude Code starts.

   export TYPESAFE_API_KEY=<your key>

2. Install the plugin.

   /plugin install dotclaude-jev@dotclaude
   

Each call sends the data of the decision to the TypeSafe API. See Second opinion.

Install the modder plugin

/plugin install dotclaude-modder@dotclaude

Enter your fal key in its fal_key option to generate assets with fal. See Modder.

Update

1. Update the marketplace and the plugin.

   claude plugin marketplace update dotclaude
   claude plugin update dotclaude@dotclaude

2. Restart Claude Code, because a running session keeps the old hooks and agents.

3. Read the new entry in the CHANGELOG.

4. Run /dotclaude:setup again. It shows each change.

Warning: Before 1.0, a release can change or remove behavior without a compatibility layer. Release 0.27.0 rebuilt the core plugin from an empty tree. It removed the 0.26 options, hooks, Terms of Use, evals, and most skills. The setup skill removes these 0.26 leftovers from your settings: includeGitInstructions: false, autoCompactWindow, the 0.26 subagentStatusLine, and the 0.26 CLAUDE.md block.

Try an unreleased checkout

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

For a separate config, see Sandbox.

Troubleshooting

Symptom	Cause and fix
No ask for a recursive rm outside the project	Claude Code does not load hooks modules in your mode, for example --bare.
No policy ask for a repository of another owner	gh is not on PATH or has no login. The ask fails open and the call goes on.
Jev calls fail	TYPESAFE_API_KEY was not set when Claude Code started. Export it and restart.

Next steps

• Quickstart: see what happens in a first session.
• Parts: see each part of the core plugin.