Muse Code works in the terminal on the repo. Grok Bot runs the rest of the desk.

One is Meta’s CLI coding agent on this machine. The other is a desktop assistant with its own computer, browser, and connectors — plus scheduled routines that keep going while you’re away.

See the comparison ↓

Where they work

Terminal workspace

Muse Code is a terminal coding agent with a native CLI named muse. It edits files and runs commands in a local workspace. An interactive session starts with muse; a headless prompt runs with muse exec.

Desk and connectors

Grok Bot is a desktop assistant with its own computer and browser, separate from the user’s machines. It talks in chat, can speak scheduled notes as voice plus text, and connects to Gmail, Google Calendar, Google Drive, GitHub, and X.

Five-hour window vs always-on routines

Muse Code on the Power Usage plan works inside a five-hour window; when that window is spent, the only move is to wait for refresh. Grok Bot runs scheduled routines while the user is away, and can launch Cursor cloud agents to change a repository and open a pull request.

Compare

Side by side, using only how these two are set up here.

	Muse Code	Grok Bot
Where it runs	On this computer, as Muse Code 1.4.2, through the native `muse` CLI in a local workspace.	On its own computer and browser, separate from the user’s machines. Talks in chat.
What it changes	Edits files and runs commands in the local workspace. Interactive with `muse`; headless with `muse exec`.	Connects to Gmail, Google Calendar, Google Drive, GitHub, and X. Runs scheduled routines while the user is away. Can launch Cursor cloud agents to change a repository and open a pull request. It is not a terminal coding agent and does not replace Muse Code for in-repo CLI work.
How you pay	Ofonime’s plan is Power Usage, $50 per month. Meta documents it as 20 times the Everyday Usage plan. Everyday Usage is documented as about 10 to 50 prompts every 5 hours. The subscription works only through the Muse Code CLI after a browser sign-in to a Meta Model API account. Creating an extra API key bills pay-as-you-go and is not the subscription.	Separate from the Muse Code CLI subscription. Muse Power Usage and Meta Model API pay-as-you-go keys do not apply to this desktop assistant path.
What happens at the limit	Power Usage is inside a five-hour window. When that window is spent, the only move is to wait for refresh.	Keeps scheduled routines running while the user is away. Can also speak scheduled notes as voice plus text.
How Ofonime uses it	Terminal coding agent for in-repo CLI work on this machine — file edits and commands in the workspace.	Runs a set of teammate assistants; Ofonime talks to them through one of them, Enquiry.