---
title: OpenPlanr in Claude Code
description: Install OpenPlanr's skills as a Claude Code plugin, invoke them as slash commands, and let Claude see every skill from CLAUDE.md.
url: https://openplanr.dev/docs/hosts/claude-code
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/hosts.md
  - https://openplanr.dev/docs/hosts/codex.md
  - https://openplanr.dev/docs/hosts/cursor.md
---

# OpenPlanr in Claude Code

In Claude Code, OpenPlanr's skills arrive as one plugin named `planr`. Every skill runs inside Claude Code. Skills and the openplanr CLI add no model calls or telemetry.

## Install

Run the setup step from [Install and set up OpenPlanr](https://openplanr.dev/docs/get-started/install.md) and choose Claude Code. Setup shows exactly what it will write before it writes anything. It installs the plugin at user scope by default, once per machine; project scope installs it into the current repository instead.

Restart Claude Code after setup so it loads the new skills. Several skills call the `openplanr` CLI, so keep the CLI installed.

## Invoke a skill

Type a slash and the skill's name. Claude Code also picks a skill on its own when your request matches the skill's description, and when a skill needs a decision from you, it asks with Claude Code's native question prompt where one is available.

Plan, Design, Status, and Doctor keep the plugin's `planr:` prefix, because Claude Code has built-in commands with the same names. A bare name runs a plugin skill only when no other command already uses it, so if a bare command runs something else on your machine, add the prefix.

Set Commands for to Claude Code, in the page header or in the navigation menu on a phone, and every skill command in these docs shows its Claude Code form, with the prefixed form in the note under it.

## Let Claude see every skill

Generate the guidance so Claude knows every skill and when to reach for it:

```bash
openplanr rules generate --target claude
```

This adds an `## OpenPlanr capabilities` section to `CLAUDE.md` between managed markers. Your own content outside the markers is left alone.

## When something goes wrong

- **A skill is missing.** Run `openplanr doctor --json`, which lists every managed installation. Confirm that setup targeted Claude Code with the scope you expect, then restart Claude Code.
- **Setup cannot inspect plugins** (`E_CLAUDE_PLUGIN_INSPECTION_FAILED`). Update Claude Code so its plugin manager is available, then run setup again.
- **Doctor reports `runtime-claude-plugins`.** The installed plugin does not match the compatible release. Run `openplanr runtime update claude --scope user`, review the listed operations, and restart Claude Code.
- **You want to remove it.** `openplanr runtime remove claude` deletes only the files OpenPlanr wrote and still recognizes. Modified or unknown files are reported and left in place.

More fixes are in [Troubleshooting](https://openplanr.dev/docs/get-started/troubleshooting.md), and [the host matrix](https://openplanr.dev/docs/hosts.md) shows what differs between agents.