Praxis

Appearance

Update Praxis ​

Update now (0.1.0-alpha.49.2, security patch). In 0.1.0-alpha.48 to 0.1.0-alpha.49.1, a repository's Claude Code settings could approve Praxis's protected actions by themselves. Update every Praxis plugin, and the Desktop extension if you use it. See the release notes and security advisory.

Plugins (Claude Code, Desktop Code, Cowork) ​

Updating from an earlier alpha (for example 0.1.0-alpha.49.1) is an update in place:

  1. Refresh the marketplace and update the plugins. In the Claude UI use Customize → Plugins and update Praxis and each Praxis plugin it installed. From a terminal, update the marketplace and all six plugins:

    bash
    claude plugin marketplace update praxis
claude plugin update praxis@praxis
claude plugin update praxis-runtime@praxis
claude plugin update praxis-ba@praxis
claude plugin update praxis-architect@praxis
claude plugin update praxis-developer@praxis
claude plugin update praxis-quality@praxis

    Updating praxis@praxis alone does not update the Runtime and roles it installed. If you installed a single role, update that role and praxis-runtime@praxis.

  2. Restart Claude (or reload plugins) so the new Runtime starts.

  3. Run praxis_doctor and check build.version is 0.1.0-alpha.49.2. In the Claude Code CLI approval.mode is client-ui; if it is no-dialog, approval.dialogAutomation names what Praxis found (Troubleshooting).

If you installed only a role before, it keeps working: it now also installs praxis-runtime as a dependency. If you had installed praxis-runtime separately, the same command updates it. A preview created on the previous Runtime must be created again before applying; do not reuse an old fingerprint. Work items and decision journals written by 0.1.0-alpha.49.1 are read unchanged.

Verified on Claude Code CLI 2.1.314 against the published marketplace: all six Praxis plugins 0.1.0-alpha.49.1 updated in place to 0.1.0-alpha.49.2 with the commands above. The update flow in the Claude interface is not yet verified.

After the update, protected actions are approved only in the client's own dialog. In Claude Desktop (Chat, Cowork, the Code tab) they are not executed; apply them from the Claude Code CLI (Approvals).

Claude Desktop Chat (MCPB) ​

  1. From the Praxis Runtime GitHub Releases page, download the new praxis-runtime.mcpb; check release-meta.json and the SHA-256.
  2. In Settings → Extensions, install it over the old one. Your settings are kept; re-enter a token if a field is empty (Praxis does not promise that every Claude Desktop update preserves user_config). The extension has no approval settings any more: a value entered earlier in Approval mode is ignored.
  3. Quit and restart Claude Desktop, then open a new Chat or Cowork session.
  4. Call praxis_doctor and compare build.bundleSha256: for 0.1.0-alpha.49.2 it is 5ced36fb3f63004e6961003e448db158432e5ffe5b10f71cee2d64c6664dc685 (the Runtime inside the .mcpb, and the same file in the praxis-runtime plugin). build.coreBaseline is 984d4f4058fbc0194def498bcb68bd0d852cbfba. One version string can name different builds, so always compare it.
  5. If you uploaded role ZIPs, update them the same way you first uploaded them.

Role plugins must stay compatible with the Runtime. Mixing a newer role with an older Runtime without checking release-meta.json is a frequent cause of missing tools. Do not leave multiple Praxis Runtime copies enabled; installing both the marketplace plugin and the MCPB in the same client gives two servers with the same tool names.

Old approval components ​

Earlier unreleased builds could include a native approval service, a broker or an installer package. 0.1.0-alpha.48 and later need none of them, and nothing is removed automatically.