v0.2.0

t3code can now work with threads that already exist. Before, it could only start new ones.

Existing threads

• threads list finds threads by project, folder, or status. threads inspect shows a thread's workspace, branch, model, turn count, context use, and any approval or question it waits on.
• threads read prints the transcript grouped by turn. --detail answers|messages|full, --turns, --first-turn, and --max-chars set how much it returns.
• threads send starts a turn from --prompt, --prompt-file, or --stdin. It succeeds only once T3 shows the message. Add --wait to wait for the turn that handles it and print the reply. threads wait waits for whatever the thread is running.
• threads send refuses a busy thread with THREAD_BUSY and sends nothing. Pass --if-busy inject to send into the running turn. Sending to a settled thread asks for confirmation, or --wake-settled in scripts and JSON mode. Archived threads are rejected.
• threads set changes a thread's model, thinking effort, speed, other model options, permission, and plan mode. threads send takes the same flags. The CLI checks each value against T3's model catalog, which models list prints.
• threads interrupt, approve, decline, and answer act on a running turn and on pending approvals and questions.
• threads settle and threads unsettle change settlement without starting a turn.

Thread commands exit with 3 for a missing thread, 4 for a lifecycle or confirmation refusal, 5 when T3 accepted the request but the CLI could not verify the turn, and 6 when a wait timed out.

Agent skills

The package ships a second skill, skills/t3thread. $t3thread <thread-id> <instruction> points an agent at an existing thread. It can brief you on the thread, answer questions about it, continue or review its work, or message it and wait for the reply. The use-t3code-cli skill covers the new commands.

Changes to existing behavior

Usage errors, such as a missing required option, now exit with code 2 and the code INVALID_USAGE. With --json they print the usual error envelope. In 0.1.3 they printed commander's plain text and exited with 1. The JSON envelope is otherwise unchanged, and the new commands only add fields and error codes.

0.1.3 never reached npm because its publish job failed. This release includes its fixes, listed under v0.1.3.

Thanks to @mhmdkhalaf for the first thread messaging commands (#1), and to @jarekbird for the busy-thread proposal (#2).

Full change: #1, #7, #8, #9