pstack-runtime
pstack-t3 runtime
pstack-t3 runs inside T3 Code. Every provider T3 drives (Claude, Codex, Grok, Cursor, Pi, OpenCode, Muse, ACP agents) gets the same t3-code MCP server. This file maps each pstack concept onto those tools, so a skill works the same whatever model runs it.
Tool names may carry a harness prefix, such as mcp__t3-code__delegate_task or mcp__t3_code__delegate_task. The semantics are the same. If a T3 tool this skill names is not in your tool list, find it with the host's tool search when the host has one, and call it by the name the search returns. When the host has no tool search, call the tool directly. Start with orchestrator_capabilities, and do not conclude the tools are missing until a search or a direct call has failed. ACP agents that cannot see the tools use the terminal bridge in ACP fallback.