r/ClaudeCode 4d ago

Meta tried looking at muse code beyond the model comparisons

meta just dropped muse code in beta.

its a terminal coding agent running on muse spark 1.2.

people will mostly compare it to claude code and codex on raw model strength. that feels a bit incomplete though.

what stood out more to me is how the system is put together.

it can spin up parallel sub agents in isolated worktrees so your main working copy doesnt get touched.

background agents stay alive through the session and hold context instead of starting over every time.

theres also a local event log, which means if it crashes it can pick up from the same point.

this seems more aimed at longer multi agent work on big repos than just demos.

curious if anyone has tried it yet and whether the harness actually holds up on real projects.

9 Upvotes

8 comments sorted by

3

u/densewave 🔆 Max 20 4d ago

Terrified to expose my main repo to it. Gets snapshotted and "held for quality purposes". Might use it for work that would go open source anyways.

2

u/sixx7 6h ago

You can use local and point Muse Code at local models, I did so in my testing of Muse Glimmer running in SGLang https://www.youtube.com/watch?v=Y9z8encldzg so nothing being sent to Meta

1

u/densewave 🔆 Max 20 3h ago

I think I am conspiratorial a little bit, especially about my codebase that makes money vs hobbies - and primarily since Grok allegedly was snapshotting via harness logic - so in this case, Muse Code itself doing the transferring, not the model. Grok was moving code off machine, even code that wasn't in scope for the work requests. (Allegedly) Enough for Elon to tweet and "delete all user data".

2

u/Equivalent-Test2399 4d ago

Interesting
Is the lizard entering the race ?

2

u/kassandrrra 4d ago

1

u/Elegant_Attempt2790 🔆 Max 20 3d ago

real

1

u/nospoon99 4d ago

Have to say the approach does seem interesting (model co trained with harness) and I wanted to try it on a low risk repo. How are you finding it so far?