T3 Pstack

t3-pstack

pstack for T3 Code. It is Lauren Tan's (poteto's) pstack, with its Cursor mechanics rewritten in place for T3. Every subagent, panel, fan-out, schedule, and PR watch dispatches through T3's t3-code MCP tools, so an interrogate, arena, or architect panel can run Claude, GPT, and Grok reviewers side by side, from a Claude Code thread or a Codex thread.

The skill text is Lauren's. A generated set of substitutions rewrites only what names Cursor (its Task tool, its model slugs, its .mdc rule, its cloud agents, /loop), and a few declared forks carry what a substitution cannot. Nothing else needs loading: the T3 rules sit where Lauren's dispatch rules sit.

t3-pstack works only inside T3.

Install, update, and check

npx -y github:chhoumann/t3-pstack runs the installer from the latest commit on main. That is the rolling channel, the same one each home's marketplace auto-updates from. To run one release's installer, name its tag, as in npx -y github:chhoumann/t3-pstack#v2.2.0 doctor.

install and update are the same command, and a second run changes nothing. With Node 20 or later, it installs or updates the t3-pstack@t3-pstack plugin in every Claude Code and Codex config home T3 can run: ~/.claude and ~/.codex, $CLAUDE_CONFIG_DIR and $CODEX_HOME, and the home of each claudeAgent and codex instance in T3's settings, disabled ones included. Name any other home with --claude-home  or --codex-home . Each home's t3-pstack marketplace must come from chhoumann/t3-pstack, or from --source  on the same run, and a home whose marketplace has another source is left as it is. A local directory needs a path such as ./t3-pstack, since owner/repo always means GitHub. On Codex it also trusts t3-pstack's session-start hook, once its hooks file is the one this release pins. Codex…