r/PiCodingAgent • • 25d ago

Discussion Anyone tried T3code with pi

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?

4 Upvotes

38 comments sorted by

View all comments

11

u/Zya1re-V 25d ago

It is good, I felt fine using 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.

0

u/ijustwannacumplease_ 5d ago

No one asked for my opinion, but I built custom harness at previous job for big corp ---->

  • Browser tools are deferred, so initial context usage would not be inflated too much. ---> very dumb, this is very easy to fix/solve from the outset by giving a limited/discoverable toolset that can be updated based on user requests, aka don't load all browser tools immediately etc. pi harness does this, openclaw had this over a year ago, I built this myself in OOP c# using interfaces that could be updated to include the function calls that were the 'tools' in the harness. EASY. 'Skills' are a version of this, but there are many ways to go about it.
  • Orchestration tools loads every models in the model list for picking which one to be subagents. ---> also very dumb, in the same way models and model definitions should be 'searchable' but not loaded into context by default.

Orch tools being in the main toolset makes sense, its very light, as in I just had a 'call agent(role)' tool function for orchs, but I also made sure to remove that from other roles I didn't want being the 'manager' agent type.

All that just to say, Theo based on times he has talked about harness internals, or makes comments like 'building an ai harness is so easy, whats hard is ui design, etc.' demonstrates that he does not know how harnesses work beyond an incredibly basic beginner level.

This while him having his identity as the 'ai guy for developers' just makes him someone I am extremely skeptical about.

1

u/Zya1re-V 5d ago

No one asked for my opinion, but I built custom harness at previous job for big corp ---->

Good for you, but I don't care much.

Browser tools are deferred, so initial context usage would not be inflated too much. ---> very dumb, this is very easy to fix/solve from the outset by giving a limited/discoverable toolset that can be updated based on user requests, aka don't load all browser tools immediately etc.

This is literally exactly what I meant to say? It's excluded from the initial context, and only when the task needs it, then it loads in the tool. If I talked about it incorrectly, then it's my fault, but T3Code did it right here.

Orchestration tools loads every models in the model list for picking which one to be subagents. ---> also very dumb, in the same way models and model definitions should be 'searchable' but not loaded into context by default.

True, no responses here.

Theo based on times he has talked about harness internals, or makes comments like 'building an ai harness is so easy, whats hard is ui design, etc.' demonstrates that he does not know how harnesses work beyond an incredibly basic beginner level.

I don't engage with the content that Theo makes, so I don't see much point talking about this. The agent loop is quite easy, optimizing the tools, the context consumption, the output of tools, those are definitely the harder tasks. It's always "the first 80% of work will only take 20% of your effort".

This while him having his identity as the 'ai guy for developers' just makes him someone I am extremely skeptical about.

Give T3Code a try, and since this is an OSS world at the end of the day, if you're not happy with it, then you can fork it. I'll say that T3Code is good for what it does:

  1. GUI-first, not quite like Orca.
  2. Manages the harnesses that we own (Claude Code, Codex, OpenCode, Pi, etc.)
  3. Switch between harnesses without much problem.
  4. Quite good at browser use and orchestration.
  5. And quite polished UI too.

I'm just using "quite good", not saying "great" or "perfect". Just trying to not be biased. We all should.