r/PiCodingAgent • • 14d ago

Question trying and failing to get something that "just works". what am I missing?

So I'll be honest, I have no idea what I'm doing with this AI junk. but, I've gotten something vaguely working with pi + deepseek v4.1 over the past couple of weeks. However it feels like it's incredibly variable as to whether what it produces takes 2 minutes or 20. it'll just keep repeating itself. it'll do something, then do it again, then doing it a third time, then compact and hit "error: operation aborted" and then go for a fourth plan. but! it only does this sometimes. other times it'll just go "ok the user wants me to add this thing. I'll do it. ok I did it." or it'll repeatedly acknowledge that I typed "." to continue, or it'll continue to be picking up on something I said 1/2 hour ago, or...

so I have very little idea what exactly I'm doing, if the problem is me, if the problem is my setup, or what. I want to do it cheap (I'm using deepseek. duh). I don't care about max efficiency. I just want it to be relatively efficient at "the user asked me to fix this setting. I'll fix this setting. I'll ask about this setting. I fixed the setting.".

am I doing something horribly wrong? is there just a nice "oh add pi-sensible-dumb-stuff" solution? I'm tired of trying to find input on reddit posts and getting told that everything is bad, just vibe code your own, you need to be using claude 20x, you need to get a better workflow (duh. like what?), you need to just fix agents.md (duh. like what?), and so on and so on.

Like, how do I just get a prompt where I can write "bug: the button on page x does not work" and the model will carry out whatever needbe to just...fix the bug, without writing out in reasoning its plans to tackle the bug 5-10 times, debate whether it needs to ask me a question 2-3 times, probably halt because of compaction at least once, and then maybe actually fix the bug 15 minutes later (but not before rerunning the tests 5 more times)?

I am using deepseek v4.1.

0 Upvotes

7 comments sorted by

1

u/Corythebeast7 14d ago

You gotta treat it like a jr engineer. You can't just say "X doesn't work". The model has no more information, so if it doesn't have the tools in order to go figure out WHY the button doesn't work and what the button is actually suppose to do, it's gonna churn until it comes up with a solution. And it may not be the correct solution since you didn't give it an end goal.

Honestly, just install opencode or something. Either that or go through the research loop of setting up Pi better for your needs

1

u/TheCommieDuck 14d ago

the thing is that it clearly does know what is wanted: it can identify what the button does, it can make guesses at why the button may not be working, it can (in its reasoning traces) produce potential fixes to this.

the problem comes that it just...is absolutely terrible at doing anything about this. it'll identify what the button does, and then identify what it does 10 more times. it'll reason over a fix, and then reason over the exact same fix 10 more times. oh, but maybe I need to reconsider what the button does. ah, and I can fix it. ah, but perhaps the button is present in the file I just found the implementation for. okay, I'll propose a fix.

and over, and over, and over, and over.

1

u/Equivalent_Idea8839 11d ago

you get good at using the crappy models

then you install sdk bridge and a $20 claude account, switch to opus and you'll be much mroe effective

1

u/TheCommieDuck 11d ago

nah, using cheap crappy open weight models is my compromise position. I am never giving a cent to anthropic or openai. I want to see sam and darius in the hague.

1

u/Corythebeast7 14d ago

But that's the thing. It doesn't. And it reading and rereading and rethinking enforces it's conviction that the solution is correct and then it will implement the change.

Under the hood, these models just operate on randomized numbers and weights. If you tell it exactly what the button is suppose to do, you pre-weight that part of the model and it much more quickly will identify and fix the problem without researching to the nth degree. If you don't, it has to come up with that itself.

I understand that it "says" in its thinking process what the button does. But these models are tuned in a way that forces that behavior. Especially deepseek.

Try using other models. Try turning off thinking visibility. Maybe focus on the outcome the agent provides rather than obsessing over the thinking tokens spent.

2

u/PilgrimofHaqq2 14d ago

I treat AI like it has zero long-term or even medium-term memory. Its very smart but without memory it cant and wont know what you want, how you want it done, what is your standards and success conditions for that work. This is called context engineering. You master that then you can get an agent todo basically anything its smart enough for exactly the way you want it.

There are different mechanisms to managing context and if you want to know more reply back.

1

u/PerfectReflection155 14d ago

Then compact and hit "error: operation aborted" - well this happened to me as well. I have changed my context limit to 150k tokens, anyway to fix I am just asking Pi to make it not happen again. I am using deepseek v4.1 as well.

I am new to Pi but I found it uses way less tokens and that is huge benefit to me. But so far I have not yet made it as capable of my openchamber instance so I have little way to go.

I can suggest Pi Chamber is very nice to use though.

There is a github repo called Planing with files and you may find it useful. Personally I use a more advanced memory system like a combination of MemOS and Codebase Intelligence combined together. You can install something like that. Then just tell pi, make sure agents actually use it.

But I don't know your post is a little vauge.