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.
dezycro ships as a single Go binary plus its plugin assets (skills, prompts, hooks). This page covers the binary install channels. 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) - A Dezycro account — sign up at app.dezycro.ai. The free tier is enough to try the plugin end-to-end.
No language runtime is required — the plugin is a self-contained binary.
Install¶
All release artifacts — native packages, archives, and bundles — are published on the public releases page: github.com/Dezycro/cli-releases/releases. Pick your platform:
Homebrew (recommended):
Tarball — download the darwin archive for your architecture (arm64 for Apple Silicon, amd64 for Intel) from the releases page and extract it anywhere. See Archive installs for the plugin-root layout.
One command — detects your package manager (deb/rpm/apk/pacman, flatpak or tarball fallback):
Force a method with DEZYCRO_INSTALL=deb|rpm|apk|pacman|flatpak|tarball.
Native packages — download the package for your architecture from the releases page, then:
sudo dpkg -i dezycro_*.deb # Debian / Ubuntu
sudo rpm -i dezycro-*.rpm # Fedora / RHEL
sudo apk add --allow-untrusted dezycro_*.apk # Alpine
sudo pacman -U dezycro-*.pkg.tar.zst # Arch
The binary lands in /usr/bin/dezycro and the plugin assets in /usr/share/dezycro.
Flatpak — download the .flatpak bundle from the releases page (not on Flathub yet), then:
Tarball — download the linux archive for your architecture from the releases page and extract it anywhere. See Archive installs for the plugin-root layout.
One command (PowerShell):
Downloads the latest release, installs to %LOCALAPPDATA%\Dezycro, and adds it to your user PATH.
Chocolatey — download the .nupkg from the releases page, then install from the download directory as a local source:
Zip archive — download the windows zip from the releases page and extract it anywhere. See Archive installs for the plugin-root layout.
Info
An .msi installer is planned.
Archive installs¶
The extracted archive directory is a complete plugin root — keep the binary next to its skills/, prompts/, hooks/, and .claude-plugin/ directories (or point the DZ_PLUGIN_ROOT environment variable at them) and add it to your PATH.
Register the slash commands¶
This registers the eight slash commands and the Companion background hooks with every supported agent found on your machine. Re-running it later refreshes the registration 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. Do this once:
dezycro login # opens your browser — sign in and authorize the CLI
dezycro setup # wires up the MCP connection and saves your Companion token
dezycro login opens your browser to the Dezycro sign-in page and an "Authorize CLI" consent screen. After you authorize, the browser tells you to return to your terminal and the CLI finishes signing in on its own — no API key to copy, nothing to paste. Your session is stored in ~/.dezycro/token.json and refreshes itself.
Working over SSH?
If the CLI can't open a browser (remote or headless shells), it prints the sign-in URL instead. Open it in a browser on any machine and authorize — the remote CLI picks the session up automatically.
dezycro setup reads that session and completes the MCP wiring. If you haven't run dezycro login first, setup will prompt you to do so.
If the automatic MCP registration fails, setup prints the manual fallback — paste the command it shows into your terminal. It will include your session credentials automatically; no dzy_… key to copy.
CI and automation
For headless environments (CI pipelines, scripts), use a Personal Access Token instead. Set DZ_TOKEN=dzy_… in your environment — the CLI and MCP server both pick it up automatically.
Licensing & telemetry¶
dezycro is proprietary software, licensed under the Dezycro End User License Agreement (EULA). The first time you run dezycro setup it shows a one-line EULA notice plus the telemetry disclosure, and records your acceptance in ~/.dezycro/license-acceptance.json. The notice is only shown again if the EULA version changes. Print the full EULA any time with:
No hidden telemetry. The only data the CLI sends is the content-free usage data that powers your own workspace dashboards: request timings, HTTP status codes, token counts, and feature/mode usage events. It never sends your source code, prompts, file contents, file names, or conversation text.
See exactly what would be sent, before anything is sent:
Turn it off entirely:
With telemetry off, the CLI works normally; your workspace dashboards simply won't show usage data from this machine.
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¶
Check the binary:
Then, 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¶
Update through the same channel you installed from (new packages, bundles, and archives come from the same releases page):
brew upgrade dezycro # Homebrew
sudo dpkg -i dezycro_*.deb # deb — download the new package first
sudo rpm -U dezycro-*.rpm # rpm — download the new package first
flatpak install ./dezycro_*.flatpak # Flatpak — download the new bundle first
For archive installs, download the new archive and extract it over (or in place of) the old plugin root. After updating, re-run dezycro install to refresh the command registration. Existing settings are preserved; no manual cleanup needed.
Uninstalling¶
Remove through the channel you installed from:
brew uninstall dezycro # Homebrew
sudo dpkg -r dezycro # deb
sudo rpm -e dezycro # rpm
flatpak uninstall ai.dezycro.Cli # Flatpak
For archive installs, delete the extracted plugin root. 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. The plugin appears under the dezycro namespace and registers commands automatically — no binary download 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:
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.ai — include the command you ran and the error you saw.