Commit, push, and create a pull request
Source control and worktrees
A worktree is a separate copy of your project's files so agents can work without clashing.
A thread's Git actions commit, push, and open a pull request. Commit messages, titles, and descriptions can be generated from your changes and the thread's work. A pull request created this way is linked to the thread automatically.
T3 Code docs: source control
What it’s for
Turning an agent's work into a reviewable pull request without leaving the thread.
T3 Code docs: source control
How to use it
In the thread, use its Git actions to commit, push, and create a pull request.
T3 Code docs: source control
Let T3 Code generate commit messages, review titles, and descriptions from your changes; descriptions also draw on the thread's work, including checks it ran.
T3 Code docs: source control
Choose the writing style in Settings → Source control & issues → Commits & pull requests: Repository conventions or Custom instructions.
T3 Code docs: source control
The pull request created from Git actions is linked to the thread automatically.
T3 Code docs: source control
Theo’s tips
Rather than verifying changes himself, Theo has the agent attach a video to the pull request showing the fix works. He says that's what his team does most of the time with T3 Code.
Or just tell it to throw a video do the pull request so you know it worked. That's what we do most of the time now with T3 code. Here's a PR from Maria.
What’s changed
- Push republishes a local branch when its remote branch has been deleted.Updated Nov 14
- A failed commit keeps your typed message so you can retry.Updated Nov 13
- Pull requests that agents create from the shell are now linked to the thread.Updated Oct 27
1 earlier change
- Pull requests can now be linked to threads.Updated Aug 25
Unofficial notes. Not affiliated with Theo or t3.gg.