transcribe

T3 Code: Another Agentic GUI that is GOOD BUT NOT USABLE..

AICodeKing · 8m · transcribed 4d ago
More from AICodeKing Business
𝕏 Share ▶ YouTube 📥 PDF 🤖 .md

Section Insights

# 0:00

Introduction to T3 Code

What is T3 Code and how can it be used?

T3 Code is an open-source graphical interface for Codex, currently in alpha stage. It can be run as a web server or as a desktop application, allowing users to manage projects and interact with Codex.

  • T3 Code is in alpha and offers a new interface for Codex.
  • It can be run as a web server or desktop app.
  • Security features are lacking in the web server version.
# 1:46

Project Management Issues

What are the challenges with adding projects in T3 Code?

Adding projects can be buggy; it does not validate folder paths and fails with certain inputs like the tilde sign. Users must input full paths or use the directory selection option.

  • Project addition lacks error handling for invalid paths.
  • Using the tilde sign for paths leads to errors.
  • The interface could be improved by removing the problematic text box.
# 3:32

User Experience and Functionality

What are the current limitations of T3 Code's functionality?

T3 Code has several limitations, including unclear file change notifications and errors when trying to view patches. The UI is basic and buggy, lacking innovative features compared to other tools.

  • File change notifications are vague and unhelpful.
  • The UI is basic and has several bugs.
  • T3 Code does not offer significant new features compared to existing tools.
# 5:18

Comparison with Other Tools

How does T3 Code compare to Verdant?

Verdant is highlighted as a superior alternative, offering a lightweight interface, better project management, and more features like on-the-fly file editing and staging changes, which T3 Code lacks.

  • Verdant is more efficient and user-friendly than T3 Code.
  • It supports multiple agents and parallel tasks effectively.
  • T3 Code needs significant improvements to compete with Verdant.
# 7:04

Final Thoughts on T3 Code

What is the overall assessment of T3 Code?

While T3 Code has potential as an open-source project, it currently falls short in functionality and user experience. It needs further development to become a viable daily tool.

  • T3 Code is still in alpha and requires more work.
  • It does not offer unique features compared to existing options.
  • The open-source nature allows for future improvements.

Transcript

0:04 Hi. Welcome to another video. So, there's a new open source graphical interface for Codex with support for things like Claude code and stuff apparently coming soon. This one is called T3 code and it's by Theo. It's an alpha stage and as someone who has tested maybe more than 50 graphical interfaces by now, I have become a connoisseur in judging these graphical interfaces.

0:35 So, let's talk about it. There are two ways to use it. You can either run it as a web server with a simple command which will launch it as a web server and you can then access it in the browser. So, you can potentially host it on a server and keep tabs on it. Though, it doesn't have any security feature to maybe password protected or anything, but you can potentially use an NGINX server to add a password to it, but it would have been better to have that.

1:09 So, I guess that could be added later. Anyway, I'll be focusing on the desktop app and talking about that majorly. Both of them are basically the same. So, this is what it looks like. On the left, you have the projects that you have open and you can work on them. Almost something like the Codex app as well. Adding projects is quite buggy, though. So, first of all, it doesn't check if you actually have the folder that you are adding.

1:42 So, if you happen to add a misspelled folder or something, then it won't give you any error or anything. It will get added and then when you send a message, you get a simple Codex error and you'd have to figure out what's wrong which is not very good to see. Secondly, it also doesn't work if you put in a tilde sign and then add your project. So, I have the KingBench app in my home directory.

2:12 So, I should be able to just type tilde slash and then the project name, but that also doesn't work. It gets added, but sending a message gives you an error. You basically have to like put in the full path with your username or use the select directory option. It would have been better to just get rid of this text box for path because it doesn't really work well. Anyway, adding a project, it shows up on the sidebar and then you can create a new thread in the project and work on it.

2:46 As I said, it just supports Codex for now. You can also switch between plan and code mode and then change the reasoning effort and also enable full access or supervised access. You can also use work tree if you want and also change between branches and create work trees from different branches as well, which is great to see. On the top, you have some options. First one is quite cool, which is the action option where you can basically add a set of commands to run by clicking it or you can also make it automatically run when a work tree is created.

3:27 You can also open the project in other editors and finder and stuff. You can also commit and push with one click if you want along with it, which is not new. Conductor has it already and Verdant has it. So, it's good to see nonetheless. Apart from that, you can also see as it works here. Now, there are some major issues with it. First of all, when it changes a file, it just says file change completed.

3:57 I cannot know what files are being changed, which is very weird. For seeing the patch of the changes, you can apparently click here and see it, but it doesn't really show it up for me and just shows me this error. I tried opening and reopening and everything, but it doesn't really work. I believe it depends on the CodeX checkpoints in order to check for the differing files, and otherwise, it gives this error, which is quite weird.

4:27 I also cannot see the files changed in the tool calls, either, which is also weird. That is basically all you can do here. In terms of the UI and features, I don't really think that it brings anything super new to the table. Very basic and kind of buggy as of now. Obviously, it will get better down the line as it's open source, which I really appreciate. Things like Conductor aren't open source, and this one is, which is great to see.

5:00 However, there are some better open source options as well. Like this one is Gene. It's by the developer of Coolify. It is quite amazing, actually. I haven't got around to do a video about it, but it's actually quite good and open source. Though, just from a functionality standpoint on how to do these agentic UIs successfully, and something that I really like is something like Verdant. Verdant is not a Claude code or CodeX GUI, but they have their own harness, which is quite good, and it is like a fully graphical interface. interface, then this one is by a wide margin the best.

5:45 It does three things very well. Its agentic contraption is actually really good and it's extremely lightweight. In idle, it only takes like 100 megabytes of memory while T3 Code and even Conductor take upwards of 200 megabytes, which can be a lot depending on how you see and use it. Secondly, Verdant also does the multiple agents and things running in parallel really well. I like their UI I much better.

6:15 Basically, you get a browser-like interface here. You can change projects here like you change profiles in Chrome and it's very, very snappy. It opens up instantly and then you can create work trees in them. And then within each work tree, you can have different threads also working simultaneously and you can manage it much more easily because it flows with your brain correctly as most of us have used things like a browser for managing it.

6:46 Plus, in Verdant, you also get the option to edit files on the fly. If you want to change something and you don't have to open another editor for that. You can also stage changes and you get things like code review and you also get options like clean work tree and stuff and it's super snappy. And you can make multiple threads within work trees, which I enjoy. And I use Verdant a lot as well and probably the only one that I use.

7:17 I was using Conductor for a while, but then I left it and I just use Keelo CLI and Verdant for now. T3 Code is good, but has a long way to go for me to use it daily. It is quite a bit buggy. It only has CodeX, which I don't use. By the way, the GPT-5.4 full testing and review will be live tomorrow. I am working on testing it. And even after GPT 5.4, I'm not going to use Codex for now, at the very least.

7:50 So, yeah, that will come tomorrow. T3 code is good, but not great in the sea of other options that are already available. It brings nothing new to the table. I myself have tried to make some UIs with different things, like a superhuman style and stuff, but it just doesn't work well, and I stick to stuff made by others. But, it is open source. So, I think that you can take it forward and stuff. So, that is kind of good nonetheless.

8:22 That is majorly about it. It needs some more work for sure, and that is why it's in alpha. So, I hope that it becomes something great with new foundational stuff, rather than just being plain and simple. Overall, it's pretty cool. Anyway, share your thoughts below and subscribe to the channel. You can also donate via super thanks option, or join the channel as well, and get some perks. I'll see you in the next video. Bye.

Summary

T3 Code, an open-source graphical interface for Codex developed by Theo, is currently in alpha and offers basic functionality with several bugs. While it allows users to manage projects and threads, it has limitations in usability and lacks essential features like error checking for project paths. Comparatively, other tools like Verdant provide a more robust and user-friendly experience.

- T3 Code can be run as a web server or desktop app, but lacks security features.
- Adding projects is buggy; it does not validate folder paths or handle special characters properly.
- The interface allows switching between plan and code modes, but the UI is basic and not innovative.
- Users can create threads, manage work trees, and execute commands, but file change notifications are unclear.
- T3 Code is open-source, which is a positive aspect, but it currently doesn't stand out among existing tools.
- Alternatives like Verdant offer better performance, user experience, and additional features.
- The developer plans to improve T3 Code, but it requires significant work to be competitive.

Questions Answered

What is T3 Code and how can it be used?

T3 Code is an open-source graphical interface for Codex, currently in alpha stage. It can be run as a web server or as a desktop application, allowing users to manage projects and interact with Codex.

What are the challenges with adding projects in T3 Code?

Adding projects can be buggy; it does not validate folder paths and fails with certain inputs like the tilde sign. Users must input full paths or use the directory selection option.

What are the current limitations of T3 Code's functionality?

T3 Code has several limitations, including unclear file change notifications and errors when trying to view patches. The UI is basic and buggy, lacking innovative features compared to other tools.

How does T3 Code compare to Verdant?

Verdant is highlighted as a superior alternative, offering a lightweight interface, better project management, and more features like on-the-fly file editing and staging changes, which T3 Code lacks.

What is the overall assessment of T3 Code?

While T3 Code has potential as an open-source project, it currently falls short in functionality and user experience. It needs further development to become a viable daily tool.

© transcribe · For agents Built with care and craft by Gokul Rajaram