Install Praxis (Claude Desktop / Cowork)
For terminal work, use Claude Code CLI setup. This page covers Desktop/Cowork installation and secure extension settings; it does not use Makefile, npm, or PRAXIS_JIRA_* environment variables.
Labels below match the Claude Desktop paths documented for current Praxis Desktop acceptance (Settings → Extensions, plugin upload). Exact wording can differ slightly by Claude Desktop version and OS. If a label is missing, use the in-app search for Extensions or Plugins rather than guessing a hidden menu.
1. Obtain release artifacts
Download each product from its GitHub Releases page. Open the product link below, choose the release you need from that product’s Releases list, then download the named asset. Products publish independently — they do not share one release tag.
| Product | Releases | Release asset |
|---|---|---|
| Runtime | praxis-runtime Releases | praxis-runtime.mcpb |
| BA | praxis-ba Releases | praxis-ba.zip |
| Architect | praxis-architect Releases | praxis-architect.zip |
| Developer | praxis-developer Releases | praxis-developer.zip |
| Quality Harness | praxis-quality Releases | praxis-quality.zip |
Each release also publishes release-meta.json (version, source SHA, SHA-256, compatibility). Before installing Runtime with one or more role ZIPs, open that file on each chosen release and confirm the declared compatibility requirements for the Runtime and role plugins you plan to use together.
Install only the role ZIPs you need. Products version independently — a BA release does not require a matching Runtime or other Skills tag.
| File | What it is |
|---|---|
praxis-runtime.mcpb | Praxis Runtime — the shared engine. .mcpb is a Claude Desktop extension bundle (MCP server + user_config). |
praxis-ba.zip | BA Skills only |
praxis-architect.zip | Architect Skills only |
praxis-developer.zip | Developer Skills only |
praxis-quality.zip | Quality Harness Skills only; use its supplied access and license terms |
Quality Harness is a delivered role package. It is separate from the private Quality Platform, whose planned purpose is multi-project quality history. Harness access does not include Platform access.
Runtime and role plugins are different on purpose. The MCPB talks to Jira and the disk. Role ZIPs tell Claude how to use those tools for one job. Role ZIPs do not embed another Runtime.
2. Install Praxis Runtime
- Open Claude Desktop.
- Open Settings.
- Open Extensions.
- Open Advanced settings (if shown) and choose Install extension (or Install desktop extension).
- Select
praxis-runtime.mcpb. - Enable the extension named Praxis Runtime.
You should see one Praxis Runtime process, not one per role.
3. Configure the Runtime (Jira)
- Still in Settings → Extensions, open Praxis Runtime.
- Open Settings (extension configuration).
- Fill in:
| UI field | user_config key | Example | Sensitive |
|---|---|---|---|
| Jira Base URL | jira_base_url | https://example.atlassian.net | no |
| Jira Email | jira_email | user@example.com | no |
| Jira Project Key | jira_project_key | PRX | no |
| Jira API Token | jira_token | (paste only in this field) | yes |
| GitHub Token (Git Delivery) | github_token | (optional PAT, not OAuth) | yes |
| GitHub API URL | github_api_url | https://api.github.com | no |
| GitLab Token | gitlab_token | (optional) | yes |
| GitLab Base URL | gitlab_base_url | https://gitlab.example.com | no |
Do not put git@github.com:owner/repo.git in GitHub API URL. That is the Connect Git remote.
- Save.
How to mint the token: Jira credentials. Never paste the token into chat, Markdown, git, or screenshots.
Claude Desktop stores jira_token in OS secure storage (macOS Keychain, Windows Credential Manager, Linux keychain where supported).
4. Install role plugins
- In Claude, open Customize → Plugins (or Settings → Plugins, depending on the Desktop build).
- Choose Add / Upload plugins.
- Select one ZIP, for example
praxis-ba.zip. - Enable that plugin.
- Repeat for any other roles you need.
Each ZIP’s .claude-plugin/plugin.json must sit at the archive root. Do not re-zip a parent folder around it.
5. Confirm installation
- Confirm Praxis Runtime is enabled.
- Confirm at least one role plugin is enabled.
- Confirm Skills for that role appear (see Plugins).
- Open a new Cowork session after enabling anything (see First run).
If a Skill says PRAXIS_RUNTIME_UNAVAILABLE, the Runtime is missing or disabled. Installing another role ZIP will not fix that.
6. Why this order
| If you only install… | What happens |
|---|---|
| Role ZIP, no Runtime | praxis_doctor is absent → PRAXIS_RUNTIME_UNAVAILABLE |
| Runtime, no role ZIP | Tools exist, but you have no role Skill/prompts |
| Four Runtimes | Wrong. Uninstall extra MCP copies. One Runtime is enough |
| All open role ZIPs | Allowed for a solo operator, not required for a team role |
7. Developer rebuild (not for end users)
Rebuilders and CI pack from each product repository (npm run pack:mcpb / npm run pack:zip). Ordinary users must download from that product’s public GitHub Releases, not from monorepo Make targets or temporary CI job artifact browsers.