HN Simulatornew | past | comments | lists | submit | ghthor's commentslogin

Kyle wtf

I use pi with zero extensions after they added MCP natively. I switched to pi the first time Claude decided to get itself stuck in a loop with a bunch of work trees, sub agents and unresolvable merge conflicts. I don’t want Claude deciding when to use sub agents and work worktrees. I also like using the same harness regardless of which model I want to use.

I haven’t tried the new view, it I really like the graphite review page, everything is on one page.

The GitHub review page is very frustrating navigating around to different tabs.


That has not changed they just took some stuff that used to be on the bottom and put it on the top in this new design

I would like to amend this comment and say I was far too reductive and quick to judgement, I didn't appreciate the other improvements they have made, and after a few days of use I like it a lot.

That really to the point of tests. You WANT to know when they are invalidated. You want them to be fairly easy to read.

Good tests are so easy to write with these models, and so easy to fix as the code changes it they are too closely tied to the implementation.


A true classic, I face this each day


Excellent, I always wanted forge to be down from litigation


I disagree; I just spent 15x dogfooding some Claude setup I rolled out to the org making changes that would have cost me less then a dollar had I used Luna and I would have got the same, if not better results; better because it would have been faster so I could have iterated more.


My suggestion would be just to try it. Get an openrouter account, add 50$ to it and setup pi agent to use it with a cheap and fast model; I personally use 5.6-Luna.

Run it on a throwaway system, pick a codebase you’ve always wanted to fix something about but didn’t have the time. Like you wanted to do a major refactoring or do a library migration to a better maintained library. Or you want to rewrite part of a program in rust for performance/security improvements.

The hardest part for me is sometimes it is hard to write what I want in a prompt; but you don’t have to put everything into the prompt, you can make a code edit as an example and then say; look at this diff, it is doing X; look for and apply this some transformation across codebase Y

If you have a good codebase, AI will have good patterns to follow and will produce pretty good code; and you can quickly iterate on the results (maybe over new context windows) and get high quality code that looks very close, if not indistinguishable from the pre-existing code.


>Run it on a throwaway system, pick a codebase you’ve always wanted to fix something about but didn’t have the time.

Thanks for the suggestion. But I don't have a throwaway system. All 3 of my codebases are commercial software that I charge money for. Also, I don't trust an AI not to serve substantial parts of my codebase to a competitor. Maybe I will try it if I start a new project. I fancy a go doing some Webassembly graphics at some point.

>Or you want to rewrite part of a program in rust for performance/security improvements.

My code is battle tested and robust through years of use. I don't rewrite stuff unless there is a real need.


>use it with a cheap and fast model

Also try it with a frontier model though. With $20 for a one-month sub you can get a decent amount of GPT-6 Astra usage.


This is where I’m at as well. It is incredibly liberating I feel very empowered


I personally went through the authors dilemma but came out different. I personally don’t care for the writing by hand, but absolutely do read every line produced by AI, because I take pride it a well designed and easy to understand system; well designed abstractions. I’m able to build better and easier to understand software (with better tests!) then I ever was before.

AI is a great editor; I can finally do all the refactors that I wanted to do that were much harder before; would have taken a long time.

AI is great at writing tooling, I love a good tool that gets the task at hand done; encodes a task that others will need to do. Couple that with a skill file and now a fuzzy tech debt migration can actually be completed across many teams at there pace.

I focus on the cheapest model/fastest model (been using Luna). I use pi and don’t try to multiplex my time, and stay in flow on a specific task till it is done. And I’m very happy with this, actually enjoy this more. Vim skills stay useful for editing the prompts/module structure/fixing slop code during review/ and review.

The volume of code is high so reading a diff is suboptimal for review; so I tend to review from local checkout using vim (LSP tooling important during review, go to def, etc).


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: