thread-migration.md

Threads from older T3 Code versions

When a server first starts with the current orchestration system, it brings its existing threads forward automatically. You do not need to run an import command.

The migrated thread keeps its title, project, provider and model selection, permission and interaction modes, branch or worktree, archive state, settlement state, snooze and pin state, and linked pull request. T3 Code also brings over user and assistant messages, their timestamps, and supported attachments. Large histories may appear in stages while the server imports transcripts.

The migration does not recreate the old provider's live session. It also does not convert old run records, checkpoints and diffs, tool activity, approval history, or proposed plan history into the new format. These items may be absent from a migrated timeline even though the conversation text is present.

Continuing a migrated thread

The first new message starts a fresh provider session. T3 Code gives that session the newest part of the old user and assistant transcript, up to 32,000 characters. Earlier text remains visible in the thread, but the provider does not receive it automatically.

Before continuing a long or important thread, read the recent transcript and include any older requirements the agent still needs in your next message. Starting a new thread and pasting a short handoff is also a good choice when the old conversation contains conflicting instructions.

Keeping a recovery copy

T3 Code does not currently have a whole-thread export command. Before a major server update, stop the server and copy its userdata directory to a safe location. The default is ~/.t3/userdata; a server started with --home-dir <path> uses <path>/userdata.

If a migrated transcript is missing from the app, keep that copy unchanged. You can inspect the old transcript without starting a server against it:

sqlite3 -readonly /path/to/recovery-copy/state.sqlite

At the SQLite prompt, list recent legacy threads:

.headers on
.mode tabs
SELECT thread_id, title, updated_at
FROM projection_threads
ORDER BY updated_at DESC;

Then print one transcript, replacing <thread-id> with the value from the first query:

SELECT role, text, created_at
FROM projection_thread_messages
WHERE thread_id = '<thread-id>'
  AND role IN ('user', 'assistant')
ORDER BY created_at, message_id;

Open only the copied database. Do not edit it or point a newer or older server at your recovery copy. If the affected environment is remote, make and inspect the copy on the machine that runs that environment.