This tutorial installs the plugin, checks skill discovery, and runs one representative skill.
Install the marketplace directly from the public GitHub repository:
codex plugin marketplace add nahuelb/pstack-codex
codex plugin add pstack-for-codex@pstack-for-codex-local
codex plugin list --jsonFor development, pass the absolute checkout path to codex plugin marketplace add. Start a new Codex task after installation so the task receives the refreshed skill catalog.
codex plugin list --json confirms the plugin installation, but Codex CLI 0.146.0 has no offline runtime skill-index command. The prompt below is the manual prompt-time discovery check; the automated release smoke validates the catalog files in the installed artifact without claiming model dispatch.
Open a repository and ask for a read-only trace:
$how explain how this repository validates plugin metadata.
Codex resolves $how to the installed pstack-for-codex namespace. The response should cite code paths and separate observed behavior from inference.
The plugin works without custom profiles. To add them, run:
$setup-pstack install the pstack agents for this project.
Choose project or user scope when asked. Project scope writes .codex/agents/*.toml and .codex/pstack-models.json. User scope writes ~/.codex/agents/*.toml and ~/.codex/pstack-models.json. Setup scans both agent locations for duplicate names and refuses to overwrite unowned files.
Model defaults live in the bundled role registry. Fresh registry entries refer back to those defaults. The registry can override every single role and panel lane. Use skill-default to restore a bundled choice. Explicit requests provide model and reasoning_effort; a Fast request adds "service_tier":"priority". An omitted tier leaves inheritance unconstrained. Setup receipts describe what the installer validated. Runtime dispatch checks supported configuration and live inheritance separately, following the model policy. Missing arguments or abbreviated model lists do not by themselves prove unavailability. A partial update changes only the roles you name.
The result includes the profile paths, registry path, receipt path, hashes, and configuration status. New choices apply to agents spawned after installation.
Invoke $setup-pstack with an explicit action and scope:
$setup-pstack inspect the project profiles and their receipt.
$setup-pstack upgrade the project profiles.
$setup-pstack uninstall the project profiles.
Upgrade and uninstall touch only receipted files whose current hashes still match. A changed or relocated file produces review-required and remains untouched.