Theo's reaction to Super Zen made my whole week.
@theo Thanks for being literally my first follower on Twitter and planting the seeds for my growth. You're someone who makes me wanna keep making awesome stuff - and now people might actually use it.
Keep an eye out for more awesome things to come very soon!
I would love to be able to customize how desktop threads are named.
Allowing us to add a system prompt just for the model that names threads would go a long way.
I would love to be able to customize how desktop threads are named.
Allowing us to add a system prompt just for the model that names threads would go a long way.
@theo You should be able to save draft responses in existing threads too, and also have it auto-sync across devices - no half-written thought in any thread on any device will ever be lost.
This small feature will make t3code feel more reliable than almost any interface out there
unofficial t3 code feature request - side chats that let you highlight any phrase and pull up a temp chat to answer a specific question
Loved this feature in claude code - it's super nice to be able to quickly gain context without derailing the main convo or waiting on it.
The next big issue I had with t3 code was the appearance, and literally before I could complain on twitter everything my heart could desire has already been shipped and ready for my to play with.
Am I the only one that thinks this kind of an output is significantly worse?
Breaking things up into a unnecessary amount of short sentences immediately makes it harder to quickly read and parse.
Oh my god.
It's hard to express how big a positive impact this tip can have on your life if you talk to Claude a lot.
> Tell Claude to write in ASD-STE100, or Simplified Technical English
As a bonus, tell Claude to follow Zinsser's four principles of quality writing:
1. Simplicity
2. Brevity
3. Clarity
4. Humanity
h/t @DanielLockyer
@theo How do I use multiple claude subs in t3 code?
Fable can't seem to figure out a robust solution for me - my threads keep crashing and arbitrarily stopping due to auth issues, cos it needs to use auth tokens to allow multiple accounts, and it expires every 8 hrs (tho seems to crash/stop far more often than that).
This os the only reason I'm forced to use claude code cos fable only runs nice for long runs in there in my experience. Maybe I'm doing something wrong?
This is the right answer.
Me being obsessed with optimizing the time it takes a human to learn a new language is the reason flua is the fastest in the world, not because I have $10m in seed funding.
In the last two weeks, we merged over 250 PRs into T3 Code. Here's an overview of the most important ones.
- Added subagent and workflow observability, so you can see what your agents spawn
- Added libghostty-vt as the terminal renderer
- Added configurable fonts and sizes under Settings β Appearance
- Added project file picker (βP) and project content search (β§βF)
- Added thread search by conversation content, from the sidebar
- Added search to settings
- Added thread pinning back to sidebar v2
- Added thread snoozing and collapsible settled threads to mobile
- Added npx t3 pair to generate a QR code from a running server
- Added per-device provider settings
- Added prompt stash (cmd+S saves the composer to a per-provider queue)
- Added picture-in-picture and background preview capture
- Added Image View outputs rendered in chat
- Added thread title regeneration from the sidebar
- Added paginated thread loading with user-anchored turn windows
- Added expanded PR review context and panel tabs
- Added mobile update checks on launch and OTA updates in settings
- Added source control writing settings
- Added collapse-all and total +/- counts to the diff panel
- Shipped T3 Connect GA (no more waitlist)
- Made mobile Thread List v2 the default
- Made sidebar v2 the default on nightly and dev builds
- Removed the Build/Plan toggle; plans now fold into chat instead of hijacking the UI
- Folded legacy models into their own menus
- Cut ~300MB off the installed desktop app
- Contained renderer memory growth and made the app recover from renderer OOM crashes
- Cut websocket throughput in half, plus permessage-deflate and gzipped thread snapshots
- Stopped shipping full MCP tool results in thread payloads
- Improved mobile: sends respond instantly, thread opens stopped freezing, scroll jank gone
- Fixed iOS streaming markdown that never rendered
- Made reconnects after remote server updates much faster
- Made pairing QR codes actually scannable, with endpoint choice
- Made remote updates rollback-safe and able to run DB migrations
- Fixed threads with open PRs auto-settling out from under you
- Fixed threads drifting off their branch so PRs link to the right thread
- Fixed self-update rolling itself back on restart
- Fixed npx service updates silently leaving the old server running
- Fixed one disconnecting client blocking every other client's reconnect
- Fixed reconnect loops during server stalls
- Fixed scrolling up during a running thread snapping back to the bottom
- Fixed stopping a Claude thread showing an ede_diagnostic error
- Fixed stopped threads not settling immediately
- Fixed commit/push/PR notices showing as errors in the work log
- Fixed T3 Connect sign-in on desktop
- Fixed the t3code:// scheme on Linux
- Fixed Linux workspace icons
- Fixed invisible T3 Connect devices being impossible to see or remove
- Fixed mobile server model, worktree, and origin preferences not applying to new tasks
- Fixed Android thread search crashing
- Fixed the terminal cursor not blinking
- Fixed terminal font size resetting when splitting
- Another 100ish fixes across platforms