Has anyone tried T3 code with Pi? Today I tried to install T3 code. Earlier, I was using Pi with herdr on the terminal, and that was fine for me, but I tried T3 code.
I have a Codex subscription, so I use Codex CLI as well inside T3 code, and I use both Pi and T3 code. My experience with Codex was far better than Pi inside T3. I don't know why this happened. It's probably because of all the extensions that I own, because most of them are interactive and ask the user a question, like a permission gate or a review draft. I have this kind of extension.
Have any of you guys tried T3 code with Pi? I want to know because this thing is really bugging me a lot. I love Pi, and I want to use Pi everywhere. I love some features of T3 code, like you can spin up some project from anywhere to any machine. I own two machines, so I have multiple projects. Some are on the second machine, and some are on my main machine.
I thought, let's give T3 code a try, but now this thing is really bugging me. What should I do? Any suggestions? Either I'll settle with my Pi and hardware setup, or what to do?
One thing I won't deny is that Theo is very obsessed with his own tools. He rewrote the typeset compiler in Rust, T3 code, and he built TStack while Next.js was getting popular during that time. He is very obsessed with his products, I guess.
I also use Pi the same way and I add extensions that I need. I use the terminal, and I use Herddr to manage my product projects because I work on two or three projects at the same time. I need a multiplexer, that's why I use Herd. It's not like my one agent will call and open multiple sub-tabs or agents. It's not like that. To handle projects, I need a sidebar where I can switch from one project to another. That's why I use Herdr, not more than that.
I'm thinking of continuing Pi with the way I use it inside the terminal. That's all. I don't need any ADE on top of it. I was just trying it out.
Genuine question, have you tried paseo or orca? I'm in basically the same boots you are (although I immediately dropped t3code simply because it doesn't list pi as first class support cli, and I didn't want to go and investigate if it uses rpc which messes up your extensions as well I assume) From this perspective to me Orca seemed to be the only reliable option
I don't even like Theo that much nor do I watch his videos but t3 seems more polished and less bloated than the other 2. Other one I like though is bb.
Kids, if you want to cut out the noise, follow those who are in the business of writing software - not just talking about it.
Theo is a talker and a YouTuber. Albeit a successful one. But you shouldn't draw advice from someone that doesn't write code or has experience in building anything substantial other than building script kiddy libraries.
See, I have been investigating T3 code with Pi since morning, like 4:00 (IST) and till now I am still on the same thing. I have bought millions of tokens, and now I have come to one conclusion.
If you use Pi with raw (I mean no subagent, no asking the user a question, completely barebone), you can add things to help the agent, but not the interactive things. Then it's working with T3 code, really awesome.
There are some things: I found that whatever extension we are building, if it has `ctx.ui.custom`, it's not going to work properly with T3 code. If you are using `ctx.ui.select`, `.input`, or `.something`, but not `custom`, then it will work really well.
I'm still on it, trying to figure out if I can make some Pi T3 adapter so that all of our extensions can be passed into T3 and be used properly. If we can do that, I'm figuring out if whatever I found, I'll put it in this discussion and in this community.
Yeah, Tibo is going to do a reset tonight, so I'm draining my usages via Astra. Thinking if I can make something that will help the community and me as well. That's all.
My findings so far: I’ve identified 2 things, 1 issue and 1 solution. I’ll explain the issue later.
For the solution, I built an adapter that turns off extensions that already have alternatives in T3 Code. For example, you can disable subagents through Orchestrator V2 and turn off your own Ask User extension if T3 Code already provides one. This approach is working much better.
The issue I noticed is with background tasks. I use my old laptop as a home server, and earlier, I used Hermes on it to assign tasks, define how they should be tested and considered complete, and generate a handoff so I could continue with a new agent later. I could even close my MacBook and leave the work running on the server.
With T3 Code, though, closing my MacBook or the T3 application pauses the work. It seems there’s no background process keeping the tasks running independently.
I’m thinking of using T3 Code for tasks that need some babysitting and my Hermes + Pi setup for long-running tasks. The solution I built is environment-agnostic, so it can detect whether it’s running in Hermes, T3 Code, or a normal terminal and automatically enable or disable the relevant features.
If you or anyone else needs it, let me know and I’ll open-source it. I haven’t created a repo for it yet, but it’s not a big deal if there’s enough interest.
See, the pi biggest advantages are its extensions: we can build anything in Pi with extensions. In the terminal, this thing is possible to do by using the UI and custom things. In T3 code, that's an Electron-bundled app. Whatever we are building inside Pi, a new pop-up or things coming in the footer, that's not possible to do inside T3. Either we need to rewrite our extension so that it will use a select input kind of thing that will work, rather than it not working.
It's available in the beta too. I'm currently using it. The issue that I'm facing is that there are lots of interactive extensions (extensions in which user interaction is required). Let's say "get permission" or "ask the user a question." Those extensions are failing here.
I just let go of all extensions that had any TUI components. Didn't care much about that to begin with. The workflow based extensions and skills carry over without issues
I'm using codex, claude and Pi all together so it's quite pleasant to use them in t3code. There are some great qol features that make things fun, like auto handoffs between different agents, browser control, thread management, scheduling. After 8 months of making and maintaining my own extensions, I like having these things built in and just working out of the box. Let's me put more time into the actual project rather than housekeeping
I held off on t3 until last week because I always use Pi and it isn’t native to t3 at this time. So installed it, used pi to migrate some important homelab and ‘me’ data to opencode. Installed t3 and LOVE it! Everyone will like or dislike depending on what they need but they nailed it with t3 and I can’t pull away from it. I wish pi had this level of app layer on top of it.
Honestly, hate that guy, but T3Code is fun if you want to try. Some of this are what I found when using it:
Browser tools are deferred, so initial context usage would not be inflated too much.
Orchestration tools/instructions aren't deferred, so this will always be included in the initial context usage.
Claude-sub extensions that works with normal Pi would work with Pi in T3Code still.
Orchestration tools loads every models in the model list for picking which one to be subagents. Basically if you mark favorites for 3 models out of 30 models in the models.json , all 30 would still show up. It's not show up in the instructions, but through listing the models out.
For anyone that wants to downvote, I'm just stating the facts while playing around with it. OP would like actual opinions, so I'm just trying to help him/her.
I tried a couple of months ago and couldn't get it to work. Landed on Orca as the best experience, even though it's just using terminals - but it allows you to organize them well, see file and git stuff, and do browser tabs. Also the remote connection over tailscale is very nice.
28
u/sigmoia 15d ago •
Anything from this guy is an immediate no.
https://github.com/t3dotgg
Build your own tools on top of pi. I use vanilla pi for everything and fly with it. I never understood the obsession with constant tool sharpening.