[fikaventures]

Why

Pstack's dispatch rules assume a standalone Claude Code or Codex parent that starts subagents itself. In T3 Code, the host owns delegation, so the two sets of instructions conflict. This adds a T3 route at the existing provider-dispatch boundary. Pstack keeps choosing each role's model and effort, and T3's delegate_task starts and tracks the agents.

Closes #253.

What changed

• provider-dispatch.md gains a T3 host section. It maps each normalized claude or codex descriptor to a delegate_task target, resolves rolling aliases through orchestrator_capabilities search, and treats other providers, unadvertised models, and unadvertised efforts as dropouts. It also covers worktrees, advisory read-only lanes, /setup-pstack probes, and the T3 records that replace runner receipts.
• codex-tools.md points Codex parents to that section.
• README and CHANGES each get a short entry.

No skill or playbook body changes. Harness translation stays in the two mapping files, as UPSTREAM.md asks. The standalone runner and receipts are unchanged.

Verification

• A fresh agent that read only the new section planned six lanes against real T3 capability responses. It routed Fable, Sol, and Opus to the correct concrete models and efforts, inherit-parent to the native tool, and Grok to a dropout. Its noted ambiguities were fixed in the section.
• Two of those planned calls ran through the real T3 delegate_task: claude-fable-5-1 at effort: high and gpt-6.1-sol at reasoningEffort: xhigh. T3 reported back the requested model and options, status completed, and the expected reply. Two more live calls confirmed that a call with no target inherits the parent's model and options, and that options: {} clears them.
• An independent Codex review found three issues: a versioned model name outside the catalog, setup's CLI checks on T3, and inherited settings at effort default. All three are fixed.
• bun run static, bun run typecheck, and bun run test pass.
• The installed-plugin live gate has not run.

[mergify]

Merge Protections

🟠 1 of 2 protections blocking · waiting on 🤖 CI

	Protection	Waiting on
🟠	Queue ready pull requests	🤖 CI
🟢	🚦 Auto-queue	—

🟠 Queue ready pull requests

Waiting for

• check-success=live-gate
• check-success=verify

Waiting checks: live-gate, verify.

Automatically queue non-draft pull requests targeting main after verify and live-gate pass on the head and every review thread is resolved.

• check-success=live-gate
• check-success=verify
• #review-threads-unresolved = 0
• -draft

---

Show 1 satisfied protection

🟢 🚦 Auto-queue

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

• -files~=^\.github/
• base = main

[greptile-apps]

[Medium impact] The reviewed changes appear safe to merge once the required exact-head live gate passes.

Summary

The PR adds a T3 route at the existing dispatch boundary.

• T3 starts and tracks pstack’s Claude and Codex lanes.

_{Reviews (2) · Last reviewed commit: "Cover T3 setup probes and default effort..." · Reviewed by Greptile}

[ericlitman]

We're going to support T3 Code as a third harness, next to Claude Code and Codex, and this PR is the starting point. We'll port it to a branch in this repository with you as co-author, so it can get our live gate, and extend it there: setup on T3, and live tests from a real T3 session. Thanks for building it. We'll link the new PR here.

[ericlitman]

Ported as #272, with your commit as the first commit (author kept) and the corrections on top. We'll close this PR when #272 merges.