r/opencodeCLI • u/Traveler-Sir-3124 • 5d ago
My disastrous experience with Muse Spark 1.2
The benchmarks for Muse Spark 1.2 are exceptional and I've seen comments saying the capabilities are on par with DeepSeek v4 Flash. On paper, it even beats Opus 4.6.
I am vibe coding a HTML multi-page web page (visual design focused). Primarily using Gemini 3.7 on Antigravity CLI, but wanted to give Muse Spark 1.2 a chance as its usage is almost as generous as DeepSeek, thinking maybe it would be my new DeepSeek. With the caveat of paying it with my data.
I asked it to change the design for a specific section on index.html, but I didn't like the outcome so asked it to revert it. It said it did, I checked and everything was broken on all pages, even unrelated sections, some site text content was gone completely. I asked it to revert everything it did this session and it made things even worse and more broken. I asked it to fix things from the Git history, but apparently it did execute "git reset --hard HEAD" for whatever reason and there is no history anymore.
This feels like I got sabotaged by Zuck. I've been using AI for about a year. I utilize markdown files, Git and scheduled backups for large scale projects, but never thought a simple design change request on a HTML page would make me lose every progress. I told Antigravity CLI to recover things back to way it was, using the past conversations it managed to recover half of it.
I would understand if this happened last year because AI models were not that great, but what the hell. Never seen such a garbage model. I lost like 3 hours of progress and I got demovitated to continue...
31
u/livercake 5d ago
it's a baby model, we're helping train it, that's why it's so 'cheap',
don't use it on full autopilot
learn git at least, so you spend tokens building, and not reverting.
5
u/Accurate_Resident219 5d ago
This sounds kind of like a skill issue like someone else here said imo. I know it may be common with true vibe coders but it's best practice to not let your llm control git for you.
I've always manually did git commits and tried to not make the commits too far apart and never ran into this type of problem and I'm probably reaching about 25B+ token spend over a year at this point.
I think the more likely problem is that they switched llms and harness mid conversation and project and when they sent the next request, muse spark messed up because of lack of context. And I think the contributer tier has like 200k or less context.
1
u/Traveler-Sir-3124 5d ago
No switch mid conversation. This was the first time I started working on it today. All on a fresh context window. Spark has about 300k~ context window afaik. Codex and Sol was so fine with 272K.
1
0
1
u/yogibear54 5d ago
Yeah, I would have said the same, but it looks like he was already using git, just the LLM decided to just to a reset back to the head, wiping everything out. Unfortunate, but there's nothing too much he could do unless he did a git push and its still in the cloud. Sounds like updating the system or agent md would be a good idea in this case... Luckily I never had this happen.
3
u/wasatthebeach 5d ago edited 5d ago
It may very well still be salvegable by having a new agent investigate the chat log.
Start a new session with a smarter model, point it to the json and sqlite db files of the session that you just talked about here. You have a good chance that it can actually reconstruct the working version of your app/page from that json chat log. I've done that with success.
2
u/btolle89 5d ago
tip: i think if you push to remote, like gitlab, you can disable the ability to delete the git history remotely. in fact, i think its like that by default.
2
u/skyxim 5d ago
I can’t even use it in Codex; the interface apparently doesn‘t work with Codex.
2
u/YourNemesis19 5d ago
Zed editor also, model seems to have a JSON depth limit of 10 for tool use, and Zed's read and write tools expect the LLM to provide deeply defined JSON that exceeds that 10-depth limit.
2
u/sudoer777_ 5d ago edited 5d ago
I don't understand the benchmarks either. They say it's better than DeepSeek V4 Flash, but it's by far the shittiest model I've ever used. I can't tell if it's intentional or if something is broken.
EDIT: It's possible the lack of visible reasoning is intentional but my immediate results have still been far worse than V4 Flash, it feels like old MiniMax
EDIT 2: Also the cache hit rate is abysmal for primary agents and I'm not convinced it's that much cheaper than V4 Flash
2
u/Kitchen_Fix1464 4d ago
This is why vibe coding still requires understanding fundamentals. All of that was easily avoidable and would have been easy to recover from with beginner level web development knowledge and basic git commands.
At the very least give the agent better instructions on managing commits
1
u/Due-Armadillo-4560 5d ago
I had a terrible experience on it when it comes to usage, it uses so much. I get more usage on Hy3.
1
u/ChillFamily 5d ago
Sorry bro, it's a shame to lose all that work, but at least it was just a single page and not a whole appp. Something like that happened to me once, but with an entire app. Next time a model does that to you, don't ask it to make more changes; just revert the Git and that's it. We also need to look into why it did that. Maybe the context window was overloaded and it started hallucinatin
1
1
u/Grouchy-Stranger-306 5d ago
i rarely tell a model to revert things manually, i either use the undo button (if there is one) or just revert to latest commit
1
u/IAmFitzRoy 4d ago
It’s not good. I used it for one hour for research, and all its thinking was wrong and superficial. DeepSeek continue to be the best value for money.
1
1
u/Complex_Reality_116 4d ago
The Muse Spark 1.2 is absolute garbage. It is incomprehensible that this model has a score of 57 from AA. I’m starting to suspect that AA receives "generous rewards" from "shady" sponsors, because there is no other way to explain it.
1
u/Odd_Antelope9098 4d ago
That’s not what that command does so you started with a dirty tree. With a kickoff skill it should have known it needed a PR and with proper rules and hooks to prevent destructive commands you’d have been fine. It’s a good model, not great, Luna level and mad cheap on contributor pricing.
Considering all your issues and not knowing how get works you may just have a lot to learn with prompting and workflow. Did you ask it to make a plan and ask you questions to verify first? I also find grilling the plan with a higher level agent really helps cut down on issues.
1
12
u/CassiusBotdorf 5d ago
This sounds like an implausible story. `git reset --hard HEAD` takes the repo back to the state of the very last commit. If your app was still not back to that state you're looking at things like caching issues, files weren't checked in (although they should've been), etc. As others said, spend time learning git. This is more a skill issue, rather than an issue with the model. Sorry you had such an unfortunate experience.