Personal Productivity

How Mike P Rebuilt His Grok Bot Agent Setup in Meta Muse to Compare

Built by Mike P · · Source: X

Quick answer

Mike P runs almost everything through Grok Bot. To compare, he spent a few hours rebuilding most of those workflows in Meta Muse. That included a main agent with focused side chats, Apple Reminders access, and a custom Strava connector that Muse wrote for him.

Result: He's staying on Grok Bot. He says Muse is faster and more polished, but it can't reach his local machine, which rules it out as his daily agent.

What they built

Mike P says he has used Grok Bot heavily since a few hours after it launched. Outside of X and iMessage, he spends nearly all his phone time in its iOS app. To see how Meta Muse compares, he spent a few hours setting up most of his Grok Bot workflows again in Muse, using about 10% of his weekly usage.

How it works

According to Mike P, Muse uses a fixed "Chief of Staff" structure. A Main Chat holds the primary agent, which he named Brooke, and Side Chats act as focused arms of that agent. He made several side chats that copy the separate bots he runs on Grok Bot. He says he prefers Grok Bot's approach, where each agent is its own entity with its own avatar and personality.

  • Apple Reminders: Muse can write to Apple Reminders through a built-in connector. He uses Reminders constantly and calls this a real advantage over Grok Bot.
  • Custom Strava connector: He wanted his Strava data connected, so Muse Spark wrote him a custom connector, which he hooked up to the Strava API.
  • Virtual machine: Like Grok Bot, Muse runs on a VM. You can browse its filesystem, but you can't remote into its desktop whenever you want.

The post doesn't give step-by-step setup details.

The result

Mike P says Muse Spark is very fast and the app feels more polished than Grok Bot's. He won't switch, though. He uses Grok Bot as a remote control for his MacBook Pro, and some of his workflows need it to read files that cloud workflows drop onto that machine. Muse can't access the local filesystem, and he calls that a dealbreaker. He also points to missing integrations: there's no Cursor-style cloud agent for repo work, and GitHub, Granola and Notion connectors don't come built in.

How to build something similar

  • Before you test a new agent platform, write down the workflows you rely on so you can rebuild them one by one and compare.
  • Check early whether the agent can reach the files and devices your workflows depend on. Local access is often what decides it.
  • If a service you need has no built-in connector, try asking the agent to write a small custom connector against that service's API.
  • Decide whether you want one main agent with focused sub-chats or several separate agents, and pick a platform that supports the structure you prefer.

The original post

Here are my first thoughts on Meta Muse as someone who has been using Grok Bot almost exclusively since day 1. https://x.com/i/article/2097470811460321280 I've been using Grok Bot hardcore since a few hours after it launched. I'm running everything through it now, and live in the Grok Bot iOS app almost exclusively outside of X and iMessage. Today, I'm giving Meta Muse a quick run-through to see how it compares to the Grok Bot experience. After a few hours, i've stood up most (emphasis on most) of the things I'm doing on Grok Bot so I can compare both platforms. My current feeling after 10% weekly usage is that I won't be moving to Muse from Grok Bot, but that doesn't mean isn't clearly better in some ways. THE GOOD: Muse spark is very fast. Like, very fast. So fast that it is the single most differentiated part of the Muse experience that I've detected vs Grok Bot. It is very satisfying to chat with your agent on this platform; it just feels better than Grok Bot in every way when it comes to speed/fluidity of comms. I don't know much about Meta models/how the intelligence of Muse Spark compares to Grok 4.6, but so far I've been impressed by how easily it has handled everything I've wanted it to do for me. The iOS app feels more polished. Page transitions, fluidity in chat, animations, etc. It all just feels like a more polished app. Grok Bot is very fresh, and I believe still considered a beta product. No surprise that Meta has the firepower to deliver a polished app experience. Native Apple connectors. This is a big deal (kind of) if you are newer to agentic AI tools. My favorite component of this is "Apple Reminders" connectivity. I use this app religiously, and Muse's ability to write to it is a big advantage over Grok Bot for me. Apple health is nice if you aren't able to stand up your other wearable data feeds directly, but honestly, this wasn't that big of a deal. I wanted Strava connected, and Muse Spark just wrote me a quick custom connector that I hooked up with the Strava API. THE SIMILAR Meta Muse can hook into Stripe Link for payments, similarly to Grok Bot. Muse runs on a virtual machine, similarly to Grok Bot. You can see the VM's filesystem on Meta Muse, but you cannot remote into the VM's actual desktop interface the same way you can with Grok Bot. If Muse needs you to interact with the Linux machine, it'll give you a window in, but you can't click in whenever you want. It uses a "Chief of Staff" format by default, and does not allow you to set this up differently. You will have a "Main Chat" which is functionally similar to a Chief of Staff, and "Side Chats" which are functionally similar to Grok Bots with focused roles. Each side chat is just an arm of your primary agent (mine is named Brooke, as you can see below). If you've been following my Grok Bot journey, you'll see that I've created a few side chats that resemble my Grok Bots. Personally, I do not like this format as much. Grok Bot gets the W here for me; I prefer unique agents with unique avatars and personalities vs the single agent setup. Many won't care, but this is a negative for me. 4. Muse doesn't have a desktop app, but it does have a web app. It's light, easy to use, and straightforward. Nothing worth writing a novel about. UNIQUE TO MUSE Instead of going 100% bots, Muse is giving you the setup above, and a few extra tabs where your agent will display things you've built/worked on in your Main and side chats. Here's what the menu looks like Chat is your standard Main Chat window. To access side chats, tap the hamburger on the top left. The next window is the feed. This automatically generates a feed that caters to the things you're doing in Muse as it gets to know you. Too soon to say whether I enjoy this, but I do like the concept if it builds itself well. Ideas is a tab full of recommended use cases for Meta Muse. Nothing too groundbreaking here. Seems kinda dumb to dedicate an entire tab to this,
Mike P (@mikepat711) · September 9, 2026 · View on X

Want to build something like this?

Join Shipping Skool free: 4 live build sessions a week and a community that ships.

Join Shipping Skool — Free

More use cases

← All AI agent use cases