I've received multiple requests for access to my latest project.
I initially built it for my own needs, but I'm excited to open-source it. Please give me a day to polish the code and prepare the documentation so you have a smooth experience using it. It's time to give back to the open-source community! ✨
Stay tuned for the GitHub link.
a year and a half ago it was cursor autocomplete, finishing a function in one file and getting it wrong. now I'm wondering if there's anyone left on this planet who codes better than ai. mathematicians? designers?
before I started building I was a product designer for 7 years. it's still in my bio, but I honestly can't remember when I last opened figma. 800 commits in the last two weeks.
@abrordev1 why would you even care? we barely look at the code anymore, and worktree and branch management feels even more legacy than that. t3code and UpComputer can render this on request if you need it, but it feels a bit pointless. what am I missing?
if you delegate several tasks from one thread and they go through a process where subagents hand work to other subagents, it all comes back through the root orchestration chat. same with bb btw. works much better when subagents are coordinated by the server instead of the orchestrating model: 37% fewer tokens in my benchmark, and the chat stays free (working on a post about that). if you don't do that and prefer managing each task in its own thread, t3code is awesome
because there's no way to tell how good the code needs to be at any given moment. Astra, for example, will try to write an enterprise-grade migration for a desktop app even if you have zero real users and don't need it. but technically, if there's no migration on update and some hypothetical existing users lose their data, that's a bug. while writing, Opus decides what's worth doing and what isn't. and when you ask it to find bugs, of course it finds them. it would find them in Chrome too. you can always find bugs
@manicode@theo for me Astra is Astra, whether it's the dev or the orchestrator. it overthinks everything, and as an orchestrator it makes every worker overthink too. still the best reviewer tho
what would that look like for you? I use it the same way in my fork and honestly I don't need a fancy sidebar anymore. I just have a handful of threads that barely ever change, one for each process. each one shows which subtasks are still running and which are done, and I can click in to see the tasks and runs. curious to hear your thoughts on that
@nanobeastCSGO@maria_rcks I found it easier to just keep my own fork with everything I want in it than to try to get stuff merged. that's the beauty of t3code