Delegate scoped coding tasks to T3 Code threads over MCP
Launch a bounded coding task from an outside MCP assistant, follow its T3 Code thread, and return the result and changes for operator review.
npx skills add agentskillexchange/skills --skill delegate-scoped-coding-tasks-to-t3-code-threads-over-mcp
Invoke this workflow when an existing assistant needs to hand one repository task to a coding agent already configured in T3 Code, then collect the result without manually switching between coding interfaces. Supply an explicit project, a task brief, acceptance checks, and the permitted changes. The scope is outside-agent thread launch, follow-up, and result handoff through T3 Code’s MCP server.
What this skill actually does
Install T3 Code v0.1.9 from its release channel or start it with npx t3@0.1.9 on Node.js 20.11 or later and start its server on the machine holding the repository and an installed, signed-in coding provider. In Settings, Environments, copy the environment’s MCP URL. Connect an MCP client that supports HTTP and OAuth. The operator completes the documented access approval with the minimum mode that permits the task. Read-only access can inspect projects and threads but cannot launch work. Use HTTPS for remote access or localhost for a client on the host.
Discover the available projects, providers, and models before launching. Pass an explicit projectId, title, and task message to t3_thread_launch. Select the intended workspace strategy and keep a clientRequestId for a retry after a lost reply. Keep the returned thread identifier and follow progress with t3_thread_wait or inspect it with t3_thread_read. Outside agents must use these thread tools; tools available only inside a T3 thread have a different invocation boundary. Route permission questions back to the operator and retain the approved access ceiling.
Finish with the thread identifier, final response, observed verification results, and changed-file or branch details available for review. Check the actual diff before accepting the work; a completed conversation does not prove its tests passed. Publishing a branch or merging changes requires the task’s delivery authority. Documentation snapshot: outside-agent MCP procedure. MCP is the framework because this entry specifically invokes the remote thread tools. Runtime behavior and security were not tested during intake.