Meta's Muse Code CLI, a terminal-based coding agent launched in August, has sparked a grassroots development effort. Harjjotsinghh, a developer on DEV.to, spent a fortnight building a dedicated desktop application for the tool, driven less by feature gaps and more by dissatisfaction with the subscription billing structure.

The Tool and the Friction

Muse Code runs subagents in parallel and maintains an append-only event log that supports replay. While the model performance is praised, the billing modelβ€”starting at five dollars a monthβ€”became the primary pain point. The developer's decision to build a custom desktop app suggests that the CLI's native interface and payment flow were insufficient for daily workflows.

Billing as the Bottleneck

The source material explicitly states that 'the billing is the whole story.' This indicates that the friction wasn't technical but economic and UX-related. Subscription-based tools often face backlash when the interface doesn't clearly display usage or costs. Building a desktop app may have been an attempt to create better visibility or control over the subscription lifecycle.

Key Takeaways

  • Meta's Muse Code CLI launched in August with a sub-agent architecture and replayable event logs.
  • The subscription starts at $5/month, but billing friction drove a user to build a custom wrapper.
  • The developer spent two weeks on the project, indicating significant dissatisfaction with the native experience.

The Bottom Line

When billing UX is bad enough to make developers build their own apps, the product team needs to take notes. Meta's model might be good, but the wrapper proves the interface isn't.