Start without a project
Threads
A thread does not need a project. Each thread without a project works in its own folder under ~/.t3/scratch, whose name ends with a short id. Branch, worktree, and diff controls stay hidden there. A worktree is a separate copy of your project's files so agents can work without clashing.
T3 Code docs: thread sidebar
What it’s for
Quick one-off jobs, such as converting files, that do not belong to a repository.
T3 Code docs: thread sidebar
When to use it
When the work grows into something real, pick Turn into project from the thread's menu. The thread's folder becomes a project where it is.
T3 Code docs: thread sidebar
How to use it
Press Cmd+Alt+N (Ctrl+Alt+N on Windows/Linux), or pick No project from the project menu in a new thread's heading.
T3 Code docs: thread sidebar
Before sending, pick another machine from the machine menu if you want the thread to run there.
T3 Code docs: thread sidebar
Later, choose Turn into project from the thread's menu, then use Initialize Git to get branch and diff controls.
T3 Code docs: thread sidebar
Theo’s tips
You can start a thread with a new project: name it, pick the machine, and choose whether it auto-syncs to GitHub. This is an easy way to spin up ideas.
You can also start threads with no project or with a new project. You give a new project a name, you pick which machine it goes on, and you also pick whether or not it gets auto synced up to GitHub, making it very easy to spin up a new project on whatever machine with whatever idea you have.
What’s changed
- A No project thread can now be turned into a project.Updated Oct 29
- Threads without a project now show their machine in the sidebar.Updated Oct 8
- Threads can be started without a project.Added Sep 30
Unofficial notes. Not affiliated with Theo or t3.gg.