Theo-brainUnofficial. Not affiliated with Theo or t3.gg.
Sign inYou

T3 Code guide

Threads from older T3 Code versions

Threads

On the first V2 launch, T3 Code copies the V1 database and migrates the copy. Your threads appear automatically with titles, projects, provider and model choices, modes, branches, pin, snooze, and settlement state.

T3 Code docs: thread migration

What it’s for

Keep working on old conversations in V2 without running an import command. Stashed prompts, drafts, layout, and theme also come over on the desktop app's first launch.

T3 Code docs: thread migration

When to use it

Use it when upgrading from V1. The copy happens once, so later changes in either version do not sync. Checkpoints, diffs, tool activity, and approval history are not converted.

T3 Code docs: thread migration

How to use it

  1. Before continuing a long thread, read the recent transcript and restate older requirements in your next message. Its first message starts a fresh provider session.

    T3 Code docs: thread migration

  2. If the old conversation contains conflicting instructions, start a new thread and paste a short handoff instead.

    T3 Code docs: thread migration

What’s changed

  • On its first start, V2 copies the existing database and imports your threads; the copy is one-way.Added Oct 3

Unofficial notes. Not affiliated with Theo or t3.gg.