Install the Strata19 plugin

Strata19 runs as a local plugin beside your coding agent. Start with the host you already use; your repository stays on your machine and no Strata19 account is required for Free Local.

Before you install

• Open a real Git repository in your coding host.
• Confirm the host can install marketplace plugins.
• If Strata19 is already installed, check its version before troubleshooting the source checkout.

Codex

Run these commands in your terminal:

codex plugin marketplace add https://github.com/jordanallen87/praetor.git
codex plugin add strata19@strata19
codex plugin list

Enable Strata19 in Codex settings if the installed plugin is disabled. Codex loads a versioned package cache, so rebuilding a source checkout does not update the installed copy.

Read the Codex host guide for the desktop project pane, lifecycle behavior, and host-specific verification.

Claude Code

Run these commands in your terminal:

claude plugin marketplace add https://github.com/jordanallen87/praetor.git
claude plugin install strata19@strata19

Approve the declared plugin hooks during installation. Enterprise policy may prohibit unmanaged hooks even when the plugin itself installs.

Read the Claude Code host guide for permission and lifecycle details.

Verify the install

Open a repository and ask:

Initialize Strata19 for this repository and show me the project status.

A working installation returns the bound repository root and current project state. The response should identify the repository it bound; an accepted configuration file alone is not proof that the plugin is running.

Then continue to your first project to inspect repository reality, capture work, create a checkpoint, and verify a change.

Updating the plugin

Installed plugins are versioned packages. When a new Strata19 version is available, update or reinstall it through your host and restart the host before comparing behavior with the documentation.

If installation succeeds but Strata19 is unavailable in a repository, use Troubleshooting and include the host, plugin version, repository root, and the exact verification response.

Connected updates

See Integrations for the supported host matrix and manual MCP configuration boundaries.