# Setup Pstack > Configure which models pstack uses per role for the harness you are running in. Detects your available models and writes the portable model config that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices. - Skill: `theoklitosbam7/setup-pstack` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add theoklitosbam7/setup-pstack` - Raw SKILL.md: https://api.skillmd.com/api/skills/theoklitosbam7/setup-pstack/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: theoklitosBam7 (https://skillmd.com/u/theoklitosbam7) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/theoklitosbam7/setup-pstack --- # Setup pstack Write the pstack model config, one line per role, mapping each role to a model you can actually spawn in this harness. The skills read it and fall back to their inline defaults when a line is absent, so this is an override layer, not a requirement. ## Steps ### 1. Detect the harness Run the detection in the **harness** skill (`../harness/SKILL.md`). Every later step depends on knowing the harness, because model slugs, spawn parameters, and config mirrors are per harness. ### 2. Detect available models Enumerate the model ids you can pass to a subagent in this session. That is the dependable source. Check the harness adapter for how: Cursor's `Task` tool errors list valid slugs, Claude Code exposes `sonnet`/`opus`/`haiku`/`fable` aliases, opencode and Crush list `provider/model-id` forms, Amp routes through the Dial. GitHub Copilot CLI lists session models with `/model`; confirm subagent model choices against the active `task` tool schema or `/subagents`. If the harness also exposes a models API or CLI, prefer it for completeness. If you cannot detect any, ask the user to paste the ids they have access to. Never write a real id you have not confirmed is available. The aliases `inherit-parent` and `auto` are always valid even though they are not detected ids. ### 3. Load current state The default role-to-model mapping is the role table in the **harness** skill plus the adapter's default section. If `~/.config/pstack/models` already exists, read it and treat its values as the current choices. Otherwise start from those defaults. ### 4. Map and confirm Show every role with its current model, marking any real id not in the detected set as needing a choice. Ask whether to accept as-is or change specific roles, offering the detected models plus `inherit-parent` and `auto`, both meaning this role runs on the parent session model, as the options. Use the harness's structured ask-user operation, plain text where the harness has none. For panel roles (`how critics`, `arena runners`, `architect runners`, `interrogate reviewers`) the value is a list, and one subagent runs per entry, alias entries included, so the list length sets the count. `arena cross-judge pool` is also a list, but Arena selects one value from it whose model family differs from the parent's when possible. `swarm workers` is the default model for every worker unless a race or comparison assigns another model per arm. ### 5. Validate Every real id written must be in the detected set. `inherit-parent` and `auto` always pass. If a chosen real id is not available, stop and ask again. A config pointing at a model the user cannot use breaks every delegation that reads it. ### 6. Write the config Write `~/.config/pstack/models`, one line per role, using the same labels poteto-mode uses. Overwrite the whole file so re-runs stay idempotent. Shape: ``` # pstack model configuration. One line per role. Delete a line to fall back to the adapter default. # `inherit-parent` or `auto` as a value: the role runs on the parent session model. Alias entries in a panel list still count toward its fan-out. code: fast: judgment: hardest: how explorer: how explainer: how critics: why investigators: why synthesizer: reflect tooling: reflect judgment: arena runners: arena cross-judge pool: swarm workers: architect runners: interrogate reviewers: ``` On Cursor, also write the mirror `~/.cursor/rules/pstack-models.mdc` with `alwaysApply: true` and the same role mappings. Cursor reads this mirror automatically. On other harnesses, use the exact user-level instruction file named in the adapter's Config section. Create the parent directory and file if missing. Preserve existing instructions. Add this line once, or update an existing pstack models-config instruction to match: ```text Before selecting models for pstack roles, read `~/.config/pstack/models` if it exists. ``` Use the user-level file so the instruction applies across projects. This step configures model-role lookup. Skills, personas, and playbooks still use their own invocation instructions. ### 7. Confirm Tell the user the exact config path and instruction-file or mirror path written. Explain that later sessions read the saved model choices when selecting models for pstack roles. Re-running this skill updates those choices. ### 8. Offer a verification skill (optional) Check whether the project has a way to drive the real app for proof, a `verify-*` skill or an existing harness. If not, offer once: "want a project-local verification skill, so agents can drive the app the way a user does and prove changes work? I can generate one with /create-verification-skill." On yes, invoke `/create-verification-skill`, which resolves wherever pstack is installed. On no, move on without pushing.