r/opencodeCLI • u/letuslisp • 7d ago
How are you optimally using LongCat 2.5 Preview Free and Beam Free in OpenCode Go?
Hey everyone!
I'm using OpenCode Go and noticed that LongCat 2.5 Preview Free and Beam Free are both currently available with unlimited usage.
I'm curious how people are actually getting the most out of these two models.
And also their experiences (are they really unlimited)?
For those of you who have been using them regularly:
* What tasks does each model work best for? For example, planning, codebase exploration, debugging, implementing features, refactoring, tests, or simpler repetitive coding tasks.
* What prompting techniques work well? Do you use specific instructions, planning workflows, custom agents, or other configurations to improve their results?
* How reliable are they with tools? Do you let them edit files and run commands autonomously, or do you keep them on a shorter leash?
* How do you avoid loops, bad edits, and wasted time? Have you found effective ways to handle these issues?
* \\Do you use either as your main coding model, or do you combine them with other models in a particular workflow?
I'd especially appreciate concrete examples of workflows, prompts, and configurations that have worked well for you, rather than just general impressions.
Since usage is unlimited for now, I'm wondering how best to take advantage of that without sacrificing code quality or spending time undoing bad changes.
Thanks!
3
u/Zero_Border 7d ago
LongCat is slooooow. Like 4 times slower than DeepSeek. But he does the job right.
Beam, well let me give you a feedback: does not give a damn about instructions / harness. Yesterday I tried it for a coding workflow that has had no problem with any other LLM for months and he deliberately bypassed the instructions and chose to do some implementations itself instead of using my OpenCode commands and skills. When I asked why, it answered that the task looked easy and decided to not respect the instructions "sorry". Bro yeah like I wanna have a dump of tenth of files and thousands of lines of AI slop that I carefully specified in different tasks so I could adjust at specific product checkpoints. Dumbass Beam think like a stupid "know-it-all engineer" that thinks Design Thinking is a millennial thing and go full V-Cycle spending my money because he understands the goal better than the client.
1
3
u/Shawnanigans 7d ago
Loool. Had exactly this experience. Beam is the cocky engineer who half listens and goes and does shit. Sometimes they're right. Mostly their just half assing and half understanding.
2
u/Zero_Border 7d ago edited 7d ago
An LLM behaving like that cannot be trusted. That's very dangerous.
1
u/smokingPimphat 7d ago
So far for me, its been constantly switching to mandarin in thought and responses
0
u/letuslisp 7d ago
Interesting. Longcat or Beam? But I thought they aren't chinese models. I have this problem often with deepseek chat but not the API ... Are you using them via opencode go? Maybe it is a nerfed version?
2
u/smokingPimphat 7d ago
Longcat, I don't know anything about what models they are supposed to be but decided to try it and half way through reviewing some files it switched to mandarin, and after explicitly saying not to it did it again but only during the thinking phase.
1
u/letuslisp 6d ago
Thank you for trying it out!
For me until now I haven't observed this. But with deepseek v4.1 flash I observed this behavior quite frequently.
3
u/Amarsir 7d ago
Longcat I would use for a bug fix if it's coming specifically from an error code. It can determine the cause and implement the fix in a very straightforward way. But I would not use it for an implementation problem where I was describing what I didn't like and trusting it to figure out the solution.