pstack in Orca

pstack skills use Cursor names. In Orca, read this file once per session, then map each Cursor name in a skill with the tables below. Every Cursor-dependent line in pstack, with its handling, is listed in CURSOR-DEPENDENCIES.md. This file is the rule set those rows apply.

You are in Orca when the ORCA_CLI_COMMAND environment variable is set. Run every Orca command with that executable. Below, orca stands for it. Outside Orca, skip this file. In Claude Code outside Orca, use docs/harness/claude-code.md.

<pstack> means the folder that holds this skill's folder, such as ~/.claude/skills/ or ~/.agents/skills/. A pstack skill named name is at <pstack>/name/SKILL.md. docs/ and agents/ are not installed with the skills. Read them from https://github.com/ynginkim/pstack-orca/blob/main/<path>.

Why Orca changes pstack

Cursor's Task tool spawns a subagent on any vendor's model. Claude Code and Codex spawn subagents only on their own vendor's models, so a pstack panel such as claude-opus-5-5-xhigh with grok-4.7-xhigh-fast collapses to one family there. Orca runs Claude Code, Codex, and Grok side by side and starts any of them as a supervised worker. pstack's cross-family panels become real again.

Route each spawn

Read the role's line in the settings file (see Models). Then: