Installation¶
The Dezycro plugin adds eight /dezycro:* slash commands to your Claude Code session and runs a small background companion that quietly guards your work against silent regressions.
This page covers the npm install path. If your Claude Code build supports the plugin marketplace, you can also install through there — see Plugin marketplace below.
Prerequisites¶
- Claude Code installed (
claudeon yourPATH) - Node.js 18 or newer — check with
node --version - A Dezycro account — sign up at app.dezycro.ai. The free tier is enough to try the plugin end-to-end.
Install¶
That's it. The install registers eight slash commands and enables the Companion background hooks. Re-running the command later upgrades you in place — your settings are preserved.
Open a new Claude Code session and you should have:
/dezycro:init
/dezycro:work
/dezycro:author
/dezycro:status
/dezycro:sync
/dezycro:publish-spec
/dezycro:verify
/dezycro:import-features
Connect to Dezycro¶
The slash commands talk to Dezycro through an MCP (Model Context Protocol) connection. You only do this once:
Paste your API key when prompted — you can find it at Dezycro → Settings → API Keys (format dzy_…). The setup script wires up the MCP connection for you.
Per-repo setup¶
Inside any repo you want Dezycro to work with:
claude # open Claude Code in the repo
/dezycro:init # one-time bind of this repo to a workspace + project
/dezycro:init interactively connects the repo to your workspace and project, detects your dev environment, walks you through persona credentials, and writes .dezycro/config.json. Run it once per repo.
After that, start working on a feature:
Verify the install¶
In a fresh Claude Code session inside a Dezycro-connected repo:
If the command resolves and prints a workbook summary, you're good.
If you see "no active feature," that's expected for a first run — just pick one with /dezycro:work <feature-name>.
Updating¶
Same command as the original install. Re-running it pulls the latest version and refreshes your local registration. Existing settings are preserved; no manual cleanup needed.
Uninstalling¶
This removes the global package. Your per-repo .dezycro/ directories are yours — keep them or delete them, nothing global about them.
Plugin marketplace¶
If your Claude Code build supports plugin discovery, you can install through the marketplace flow instead of npm. The plugin appears under the dezycro namespace and registers commands automatically — no npm install and no setup steps beyond /dezycro:init.
Troubleshooting¶
"Dezycro MCP server is not configured"¶
The plugin is installed but the MCP connection isn't. Run:
and paste your API key when prompted.
Slash commands don't appear¶
Quit Claude Code completely and open a new session — Claude Code only picks up newly registered commands at startup. If they still don't appear, re-run:
and try again.
/dezycro:work refuses to start on a feature¶
By design. The plugin requires a feature to have a completed PRD, TRD, and approved journey graph before it will load the agent context. Finish the docs in the Dezycro UI, then re-run.
/dezycro:verify reports a missing authenticator¶
The verifier expects credentials for a persona that the plugin didn't manage to resolve. Re-run /dezycro:init — it walks you through persona auth setup. Full details on auth backends are in the PERSONAS guide.
Still stuck¶
Email support@dezycro.io — include the command you ran and the error you saw.