Top
Best
New

Posted by karagenit 12 hours ago

Goodbye Claude, hello Pi(caleb.software)
506 points | 329 commentspage 3
mnming 2 hours ago|
I haven't used any TUI harness for a couple of months. Actually, I have almost completely stopped using my laptop to run agents since maybe July.

All agents are ephemeral and running remotely now, and my phone has become my primary device to engage with agents.

(I'm using Ampcode and a variant of DeepSeek harness)

sergiotapia 21 minutes ago||
I highly recommend Paseo. I feel like I finally found what I was looking for after so long.

https://github.com/getpaseo/paseo

It works really well, has the nice code diff view which what I used to open vs code for, and it lets you drive from your phone.

All the beefy work happens on my machine at home with big hardware and .env secrets, etc. And from my phone I'm able to run multiple threads with multiple models/thinking modes.

I think a testament of how useful it is, is everybody on my team switched over to Paseo pretty much in a week.

peteforde 6 hours ago||
I've been using Cursor for a few years now, and while I'm well aware that it's more expensive, from a UX perspective I am 95% happy. There's still a few things like not being able to move conversations between folders or computers, but big picture, a lot to love. It's just a really coherent dev experience.

When I read what folks write about CC and TUIs it all sounds... really, really awful and I kind of don't get why any wouldn't want to use Cursor. I'm posting this to see if anyone wants to explain how/why I might want to ditch Cursor and go all in on Claude or Codex or Pi or anything else. I'm open to being convinced!

Mostly, I just want to understand. My sense of CC is that it's great for folks who are looking to spend lots of money having 4 agents one-shot an entire application from a single prompt so that they can pick their favourite when they wake up. Is that an absurd perspective? If so, tell me how you use it.

I'm someone working on fairly significant but personal projects; I have a very clear picture in my head about what I'd like to get so I tend to write extremely dense, detail-filled prompts and go through a multi-revision planning phase before kicking off agent mode on a feature. The apps I build tend to be the result of several dozen or several hundred features developed mostly serially, and I am always the bottleneck because of that whole "knowing what I want" thing.

So, that's my usage pattern. Should I be using Claude (or Pi)?

cejast 5 hours ago|
> The apps I build tend to be the result of several dozen or several hundred features developed mostly serially, and I am always the bottleneck because of that whole "knowing what I want" thing.

This is probably where the disconnect is - the TUI workflow only really clicked when I started working across multiple worktrees at the same time.

It’s not all or nothing. You can still be fully in the loop, read all the code and steer each session towards the outcomes you want. You’re just doing it across multiple branches at the same time and imo it’s easier to do that through the TUI.

peteforde 4 hours ago||
How do you stay effective when working across multiple worktrees at the same time? That is, how do you keep context in your head?

Then when it's all over, how do you evaluate which one to keep?

cejast 1 hour ago||
This is indeed a challenge and there is a practical limit to how many you can manage at once. It really depends on what I’m working on, for a sufficiently large enough project there are lots of independent tasks that can be delivered in isolation and so it’s rarely a case of babysitting all of them in realtime.

I tend to have one session that I’m actively focused on as my primary session, everything else I come back to every ~5-10 minutes to nudge them along while I’m waiting on the ‘main thread’. If my core task demands more of my time to think then I check less often.

The important thing is to find what works for you. If Cursor is giving you enough productivity then that’s awesome, carry on with it! I would recommend trying out other workflows, weighing up the pros/cons yourself and ultimately find what works for you. TUI-driven development isn’t for everyone in the same way not everyone likes to use vim and that’s okay.

justauserid 11 hours ago||
> having a ton of CLAUDE.md files scattered about various GitHub hobby repos is great guerrilla marketing

Their real marketing comes/came from https://github.com/claude phenomenon. Irrespective of what underlying model you are using the claude code harness just sticks this github user as git commit author and then you have to make an effort to remove it. That is just odd.

senko 6 hours ago|
Agreed that it's annoying by default, but it's quite easy to disable: https://code.claude.com/docs/en/settings-reference?ref=expla...
gregwebs 3 hours ago||
I have been using Pi most of this year. Just one problem that's going to make me move to deepseek harness: no subagent support. I am using tintinweb/pi-subagents and it works, but always wondering if there is a better option. It doesn't seem to work right with Herdr's agent status.

I have a plugin for rotating between providers as quota gets used up by altering the model used by the tintiweb subagents. https://github.com/gregwebs/pi-quota-dispatcher

neop1x 2 hours ago||
I am using https://github.com/melihmucuk/pi-crew which I like more. It has pretty nice pre-defined agent .md files. Then there is also https://github.com/nicobailon/pi-subagents . It is probably worth trying all three and decide. But pi-crew is a winner for me personally.

Note that there is another extension called pi-crew which mentiones in Readme that it was completely vibecoded, I haven't tested that one.

oddly 3 hours ago||
I've been using pi-optchat, might want to give that a try. Manually connecting subagents to the main agent keeps them open indefinitely. https://github.com/jonaslsaa/pi-optchat
adamisnotroman 2 hours ago||
Yes, I'm the same. As for any feature that CC has, you can build it with one prompt with the Pi extension system. For remote control you can just use Cosyra (my app) or one of the other SSH mobile clients.
y42 5 hours ago||
I built myself a tool because of the exact same reason:

https://github.com/nickyreinert/yaw/

I was struggeling with multiple markdown files, not only for multiple Claude sessions, but also Copilot and Codex, accross different machines and projects with diferent purposes.

The problem: This is not only about some pre-prompt instructions, its about coding instructions for different lanugages, frameworks and architectures and skill/hooks/tools for different purposes. I drowned in multiple setups (I have ADHD/ASS, I start two projects a week). So I decided to built this kind of "wrapper" that I can use with every new project. It allows me to maintain a global setup of "defaults" and then add modules to each project as I need them.

It's not fully done now, but it already helps me. Someone else might find it useful.

4dregress 6 hours ago||
As someone who spends a significant time in the terminal (iterm2), I just have Claude sessions open in tabs when I need it.

My setup is Pycharm, datagrip and iTerm2.

I run all the tests, debugging, linting in the terminal and use the jetbrains gui features which I find useful (some git management basically).

It works great, and this is for building large enterprises applications.

smcleod 6 hours ago|
Try and get on the early access waitlist for Rex, really nice terminal + multiplexer. Ghostty replaced iterm for me and my team, then Rex which uses libghostty was a great level up further.
pu_pe 4 hours ago||
I use both, and I think Claude Code is easier for beginners but Pi is more interesting to get a better understanding of what the harness is doing for you. Stuff like skills and MCP are sort of abstracted in CC in ways that obfuscate things, probably intentionally, while Pi lets you really see where a model got stuck and why. Inspecting thinking traces and dead ends from local models teaches you a lot about how they work in general.
txdv 9 hours ago|
My biggest claude code problem is that it calls git status with fsmonitor turned off via env variables and command line argument and I work on a super big repository.

I'm spawning a lot of agents to work in parallel. I guess I should just use the API, but it just shows that it does some random stuff you might not agree with. 99% of the users are ok with it because they don't have a 10gb repository

More comments...