T3 Code news and changelog digest

What actually changed in recent T3 Code builds, in plain English. Nightly releases ship most days — this is the running digest of the changes worth knowing about.

Last reviewed · verified against the pingdotgg/t3code repo

T3 Code ships nightly builds most days, sometimes several. Most are small. This page tracks the ones that change how you work, with links to the underlying releases so you can verify anything here.

Recent builds#

27 July 2026 — v0.0.29-nightly.20260727.915#

  • Development instances can now be shared over Tailscale, so a dev build is reachable from another device rather than being stuck on localhost
  • The instance picker now skips browser-blocked ports. Browsers refuse to connect to certain port numbers outright, and landing on one produced a failure that looked like a crashed server
  • Read more →

27 July 2026 — v0.0.29-nightly.20260727.914#

  • Worktree dev state is kept isolated on T3 Code dev servers, so running a development instance no longer leaks state into your daily setup. Pairs with T3CODE_DEV_INSTANCE (configuration →)

25 July 2026 — v0.0.29-nightly.20260725.899#

  • Fast mode now displays as a bolt icon rather than a text label

25 July 2026 — v0.0.29-nightly.20260725.898#

24 July 2026 — v0.0.29-nightly.20260724.896#

24 July 2026 — v0.0.29-nightly.20260724.893#

  • Improved light-mode contrast for user message bubbles
  • Restored the model picker layout and retained iterative test state
  • Settled PR labels are now coloured on hover
  • Fixed glass hover compositing artifacts

24 July 2026 — v0.0.29-nightly.20260724.892#

  • Upgraded Clerk packages and the Expo integration

24 July 2026 — v0.0.29-nightly.20260724.891#

  • Thread snoozing. Push a thread out of the way without losing it — useful when several long runs are in flight and only one needs attention

24 July 2026 — v0.0.29-nightly.20260724.890#

  • Large git diffs collapse by default for readability
  • New threads no longer inherit branch settings from previous threads, which had been producing surprising commits
  • The branch-mismatch banner was toned down after proving too noisy
  • Claude Code skills are discoverable in the composer (Claude Code guide →)
  • Settled threads remain accessible rather than disappearing

24 July 2026 — v0.0.29-nightly.20260724.889#

  • Preview colour scheme controls
  • Simplified project grouping
  • Fixed a thread loading flash
  • Polished the iOS git progress overlay (mobile guide →)
  • Improved composer glass fallbacks

Patterns worth noticing#

Reading a few weeks of changelog rather than individual entries, three themes stand out:

Diff review is a priority. Collapsing large diffs, a collapse-all toggle, diff scope switching. Someone is using this on real, large changes and finding the friction.

Mobile is getting deliberate attention. An iOS git progress overlay is not something you build by accident. Combined with Tailscale work and QR pairing, the remote story is being taken seriously. Mobile guide →

Thread lifecycle is being worked out. Snoozing, settled threads staying accessible, branch settings no longer inherited. These are the problems you only discover after running many threads over many days.

Following along yourself#

FAQ#

How often does T3 Code release?#

Nightly builds ship most days, sometimes several per day. The project is in active early development in the 0.0.x version range.

Where can I find the T3 Code changelog?#

The authoritative changelog is the GitHub releases page for the pingdotgg/t3code repository. This page digests the changes that affect how you actually use the tool.

What does a nightly version number mean?#

A tag such as v0.0.29-nightly.20260727.915 indicates work toward version 0.0.29, built on 27 July 2026 as build 915. It's not a released 0.0.29.

Should I install T3 Code nightly builds?#

For personal use, yes — fixes and features arrive fast. For team workflows, pin a version, since the project warns about breaking changes.