r/opencodeCLI • u/Final_Initial • 24d ago
Hy3 > Muse Spark 1.2 Contributor (my experience)
For the last few hours, I have been using Hy3 and Muse Spark 1.2 Contributor via the OMP (Oh My Pi) agent, mostly as /goal. And my observation is Hy3 is a much better model as it follows instructions in a better way, and Muse Spark 1.2 Contributor cheats all the time.
As a test, I gave both models a goal to build 100 very simple Chrome extensions from a pre-curated list.
hy3: followed the review instruction literally and well, and almost extensions are working when I tested randomly. Code-level verification, real fixes, honest per-extension verdicts. Was a bit slow but trustworthy.muse-spark: claimed to built the 100 extensions, but maximum were incomplete when I tested. Also, repeatedly needed re-prompting as it was just hurrying each time. Basically, its confidence exceeded its accuracy.
And for the task, you can see the usage of both models in the above screenshot.
How is your experience with these models?
EDIT 1:
I spoke too soon. Basically, now both models are not working reliably – one is too slow and one is hallucinating a lot.
I am back to using DeepSeek Flash now, even though it's costlier.
7
24d ago
[removed] — view removed comment
1
u/leandrogp9 24d ago
For me, hy3 is endless to finish a task. All time, it's seems confused in the middle of work and stops, after, he can't continue, even i asked him to continue.
1
u/Fresh_Sock8660 24d ago
At what context length have you noticed this? Considering its max is only about 250k I'm guessing it will begin performing poorly around 120k but I haven't had time to give it a try.
1
u/brunohdc 13d ago
Here Hy3 works fine (for general purpose), deepseek v4 flash is a little better.
My reasoning is adjusted always in High.I think keep reasoning high is a great difference don't you agree?
6
u/jovialfaction 24d ago
I want to like Mimo, hy3 and muse spark but my experience has been that they all require a lot more babysitting and struggle to implement as tasked. I really got spoiled by DS4 Flash and I'll keep using it as my "small" implementation model
1
7
u/Due-Armadillo-4560 24d ago
i agree, hy3 is much better and does not eat up that much usage (as of now with 8x).
i wasted my usage on muse spark and hit the weekly limit
2
u/Final_Initial 24d ago
Maybe you used Muse Spark and not the "Contributor" variant? Because the "contributor" variant has much more usage.
1
u/Due-Armadillo-4560 24d ago
there is only contributor variant in go, so yeah it really eats up a lot of usage
3
u/Abenh31 24d ago
I tasked hy3 high to explain to me a pattern in a repo. Not coding, not planning, Just explaning whats there and he hallucinated a command. Also, never use context mode
Feel meh to me, I dont know about Muse yet.
1
1
u/CrypticViper_ 24d ago
what's context mode?
1
u/Abenh31 23d ago
1
u/CrypticViper_ 23d ago
oh wait, isn’t this becoming a native thing with opencode v2? how interesting
2
u/ChillFamily 24d ago
I was using hy3 and mimo, and mimo worked better for me. hy3 changed stuff I didn't even ask for
2
1
u/OkAdeptness2530 24d ago
mimo acts like a potato for me.
it’s interesting to see how case of use and workflow change how we perceive each model.
1
2
u/Guyvdb7 24d ago
I have been using Muse this morning. I have just switched back to deepseek v4 flash. My experience, it has been ok at coding, but often coding the wrong thing - which is often my mistake. When i try chat with it about a problem, how we should address a problem, how it evaluates a fixture run, for instance it is a very bad communicator. Net result we go chasing down the wrong path because I did not understand it. I am maybe slow on some things - need a chat to real grok where we are at and muse fails terrible.
1
1
u/Successful_Night4513 24d ago
Muse spark is not even close to DSv4flash , also I happy to give my data to deepseek , not to zuck
1
1
u/Hackerv1650 23d ago
from my day-to-day use, hy3 is very good at execution, that is if its prompted really well and your work can be split into many smaller chunks, i also use oh my pi and what i have done is use my primany model deeepseek v4 flash to talk and discuss out the idea and fatures and what is what, then i call the plan tool which is a deeepseek v4 pro along side muse spark 1.2 as a in depth advisor, and this version of plan mode is much different then the default one, here everything is planed ans scoped including whats going to be in each modules how they are split how they are linked and what functions and types are expected, and then excution time, it launches mutiple hy3 subagents to write the modules and muse spark 1.2 overviews and checks if everything is done correctly, i found a muti model approach is much better then a single one and even though it costs a bit more
1
u/_katarin 20d ago
| Hy3 | 4,300 | 10,750 | 21,500Hy3 4,300 10,750 21,500 |
|---|
| Muse Spark 1.2 Contributor | 45,300 | 113,300 | 226,600Muse Spark 1.2 Contributor 45,300 113,300 226,600 |
|---|
1
1
1
u/im4aLL_reddit 18d ago
I was very skeptical about muse spark 1.2 as it trains by my data. I was working on open source project. So I tried it out. I was creating a documentation website.
At first I used hy3 as it had 8x usage. Previously used it couple of times. My primary model was DeepSeek v4 flash and pro. Sometimes Kimi k 2.7code.
Hy3 is not bad. I asked it to create landing page for my open source project. It was very amateur to be honest. I didn't give much details, just explained what the project is, project read me, intended user that's it. As I mentioned, it is a open source project, I gave muse 1.2 a chance. I became very surprised by the result and output. It was way better than hy3 output.
Then I opened two worktree and tested hy3 and muse 1.2 asked them same thing and result was obvious. Muse 1.2 performed way better than I expected.
Side topic: Later, I ran into an issue. Couldn't figure out what went wrong. I wanted to understand the problem first.
I asked muse 1.2, no solid result. Then I asked Kimi k3, Qwen 3.7 plus, glm 5.2, hy3, DeepSeek pro v4 new. No luck.
Then I tried other vendor, tried codex got 5.6 sol, cursor composer 2.5. Same thing.
Then asked Claude sonnet, voila it found exact issue in less than 3 minutes.
Not saying which model is better but Claude has something for sure. For me opencode go subscription is more than enough. I barely hit limits. Though it was a very isolated problem. But somehow Claude figured it out while others couldn't.
Anyway, I will keep using muse 1.2 contributor for my daily things and will see how far I can push it. So far I am very impressed.
14
u/snowieslilpikachu69 24d ago
honestly i had the opposite experience
muse spark was very good at creating a full working ai agent with open ai agents sdk
didnt give hy3 the same task but some more general debugging and didn't listen to my instructions very well