T3 Code Thread

Read the t3code skill first.

Inputs To Resolve

Resolve these before sending anything:

• Target environment/server: httpBaseUrl plus bearer/session authorization.
• Bearer token: resolve through the t3code token cache; do not issue a new token when a valid cached token exists. Prune older launcher clients with the same label/subject when using the bundled launcher.
• Target project: project id and workspace root/title if available.
• Target thread: existing thread id, or new thread.
• Prompt text: self-contained, with files/constraints/acceptance criteria.
• Model: explicit user choice, <project-root>/.t3code/config.json, an alternate .t3code/<name>.json via --model-config, project default, or codex / gpt-5.4.
• Modes: default runtimeMode: "full-access" and interactionMode: "default" unless the user asks for supervised or plan mode.
• Worktree: use one for implementation fan-out, concurrent agents, or dirty main checkouts; use the project workspace directly only when sharing state is intentional.

If project id, server URL, or authorization is missing and cannot be discovered, ask for exactly that missing RPC input before proceeding.