How much can you actually use on Muse's free tier?
Meta doesn't publish a hard number for Muse's free tier — it's a weekly allowance that resets, well below the $20 plan's roughly 500M tokens a month. The practical advice from the thread: watch the usage meter in Settings for a week, since agentic background errands burn tokens far faster than chatting. If you're running dry before the week ends regularly, you've outgrown the free tier.
Read the story →More stories
Muse Mac app can't preview PDFs while iPhone and web work fine
A user reports PDF attachments won't preview in the Muse Mac app (Intel, Sequoia, v8.0) while the same files preview fine on iPhone and web. Their agent already ran a three-way test with differently-built PDFs to rule out the file. The thread points at the Mac app's renderer or sandbox cache, with a clean quit-relaunch and update check as first steps.
Read the source →Using orchestrators like Herdr to split planning and execution across models
A Claude Opus user asks how to orchestrate expensive-model planning with cheaper-model execution (Sonnet, Codex) without the output falling apart. The emerging rule of thumb: keep the pricey model for planning and final review, run the cheap model inside a tight test loop. The trap is paying the expensive model to fix cheap output three times over.
Read the source →Two people's Muse agents collaborated for four days through one shared Google Doc
Two Muse users had their agents co-design team posters and a handbook over four days, using a single shared Google Doc as the only channel. Every note passed through a human first, and neither agent acted on the other side's say-so. The human-gated relay killed the classic failure mode of agents hallucinating instructions from each other.
Read the source →Muse analyzed a user's raw DNA file — and found things the testing company didn't mention
A user fed their raw DNA file to Muse and got back interesting findings, including disease markers the testing company never flagged. The thread's caution: a DNA file is the most identifying upload you'll ever make, so check retention and deletion policies first. Fun ancestry-style findings are the safe part; health claims deserve a professional second opinion.
Read the source →The $10K/month n8n playbook: five automations small businesses actually pay for
A practitioner breaks down a $10K/month n8n automation agency: five productized automations for small businesses, led by AI voice reception and missed-call text-back. The math is $5,000 setup plus $2,000/month per client, with tooling costs of $400–1,200. Self-reported and unverified, but the arithmetic is unusually transparent for the genre.
Read the source →$3,850/month automation agency running on a $4.80/month open-source stack
An agency blueprint built entirely on free and open-source tooling: self-hosted n8n, a $4.80/month Hetzner VPS, Twilio, Groq's free tier and Supabase free. The flagship flow detects a missed call, sends an SMS within five seconds, has AI triage the need, and books a slot automatically. Self-reported; the uptime claims deserve skepticism, but the stack economics are the real lesson.
Read the source →An underrated freelance niche: AI-assisted QA testing for solo developers
A freelancer spotted a gap: solo developers shipping apps (one had 11k users) get buried by bad reviews because they only test manually on their own phone. The pitch is AI-assisted regression testing across devices, sold to indie devs and tiny agencies. No income figures yet — it's a niche idea from a single case — but the pain point is concrete and the buyer is easy to find.
Read the source →What AI automation agencies actually earn in 2026: operator benchmarks
A roundup of operator case studies: a solo freelancer productized document intake for accounting firms at $500–800/month per client and hit $25k ARR in four months; a niche agency reached $432k ARR with twelve $3,000/month retainers in fourteen months. The shared pattern is productize first, niche down, then acquire. Data comes via a tool vendor, so expect cherry-picking.
Read the source →Muse pauses artifact sharing after published URLs leak an index of user artifacts
Meta has turned off Muse's artifact publishing feature after a privacy flaw: published pages used URL subdomains as paths, which got cached by DNS providers and exposed a way to enumerate other users' published artifacts. The Verge reports it as a privacy incident. Sharing is paused while Meta fixes the underlying URL scheme.
Read the source →Zuckerberg: Muse will eventually earn more per user than Facebook and Instagram
On Meta's Q3 earnings call, Zuckerberg said Muse should eventually generate more revenue per user than Facebook, Instagram, WhatsApp and Messenger do today, via commerce transaction fees and subscriptions. About a quarter of Muse users shop through the agent, with average purchases above $200. The claim reframes Muse from cost center to Meta's next monetization engine.
Read the source →1Password launches '1Password for Agents' with Muse support
1Password announced '1Password for Agents,' a credential-management product for AI agents, explicitly calling out Muse support and integration rolling out in the coming days. It's an early sign of an enterprise tooling ecosystem forming around Muse. For agent operators, it addresses the sharpest unsolved problem: what credentials an agent holds and how they're scoped.
Read the source →