QWE AI Academy You finish the week with a tracker and three draft emails already waiting
Picture this: Friday afternoon, your client-call notes sit in Google Drive. By evening you have a clean action-item tracker in Muse’s Library, three follow-up drafts sitting in Gmail (unsent), and anything older than 30 days flagged. You never opened a spreadsheet. That end state is what this walkthrough optimizes for – not “try chatting.”
We’ll reverse-engineer how you get there: finished job first, then the permissions and connectors underneath. Fifteen minutes is enough for one real multi-step result.
What you’re actually running
Muse is Meta’s personal agent for long-running work on a dedicated cloud machine, not a one-prompt chatbot. The September 2026 launch post places it inside Muse Secure VM – an isolated box with its own browser, files, and terminal – so jobs keep going after you close the app.
Sentinel is a second process on that VM. It alone gates network egress and connector writes. You still approve anything that sends, books, or spends (Allow once / for task / always / Deny). As of late 2026 it ships in the US and Canada for adults 18+, on the Muse app, muse.ai, WhatsApp, Mac, and iPad.
Junior hire with a laptop and calendar access. Still asks before Send.
Practical setup that protects you first
Skip the playful first prompt. Order matters.
- Open muse.ai or the official app. Sign in with a Meta account. Name the agent and pick a tone once – it sticks.
- Settings → Permissions. Default connectors to “Always ask” (or “Ask for some actions”) before you link anything. That is your control surface on Sentinel.
- Settings → Data Controls: use the training opt-out if you do not want interactions used that way (option is in Meta’s Muse materials).
- Settings → Connectors. Add Google Workspace – or the Drive/Gmail pair you actually use – one service at a time. Read-only first. Write paths come later.
- Check the free usage meter. Meta Help: About Muse subscriptions states free with a refreshing limit; Power is $20/month for 500M Muse tokens/week; Maximum $100 for 3B/week. Features match across tiers. Exact free size is unpublished – treat the meter as truth for your account.
After the five steps, hand over the job. Loose approvals on day one is how you rubber-stamp a dozen cards at 11pm.
Pro tip: On the first three tasks, watch the live browser view or the activity log under the avatar. Silent Sentinel + zero approval cards usually means permissions are too open.
Worth a pause: the product demo energy pushes you to connect everything immediately. The useful habit is the opposite – one read path, one visible approval, then expand.
The workflow that proves it works
From my Google Drive notes on last quarter's client calls, pull open action items.
Build a simple tracker artifact in Library with owner, due date, status.
Draft follow-up emails in Gmail for each open item and hold every send for my approval.
Flag anything older than 30 days. Do not send or create calendar events yet.Muse reads via the connector, writes an Artifact you can reopen from Library, stages drafts, and surfaces approval cards. Close the app – the background thread continues and pings when it needs you. One run hits connectors, Artifacts, Sentinel, and persistent state.
Meter jumped harder than you expected? That is the real price of multi-step browsing plus planning. Chat barely moves it. Agent work does.
When one-off jobs are not enough
Goals tab next. Turn a recurring pain into a plan: “Keep the client tracker current every Monday and surface anything stalled >14 days.” It breaks the work down, schedules itself, and only interrupts on meaningful changes or approvals.
Ask it to build small VM-side tools – a spending view, a study guide – that land as Artifacts. Side chats help when one thread gets noisy. Shopping and bookings path through Link by Stripe one-time cards so the real number never sits in the agent; eligible buys keep Link purchase protections. Credentials stay in the secure store; conversations are not fed into Meta ad systems.
Honest limits you will hit
Amazon blocked Muse shopping access around 21 September 2026 as an unauthorized agent. Other retailers throw CAPTCHAs or bot walls. Muse will not circumvent them – Meta’s terms forbid bypassing access controls – so there is no in-app override. Finish that step yourself or switch merchant, then let it resume from the confirmation page.
Token burn eats free tier fast. Light errands for a week may barely register; a day of parallel research + connectors can pin the meter and force a wait or upgrade mid-goal. Paid Power/Maximum buy weekly Muse tokens only – same Sentinel, same connectors, same browser – until newer models fully finish rolling to subscribers.
Heavy parallel background jobs and long context have left some users in reconnect loops or “Getting Ready” stalls on the dedicated VM (community reports while the product is still early). Region locks are hard: unsupported countries just see unavailable. VPNs are unreliable and can flag accounts. Memory sticks until you tell it to forget. A confidential VM with a user-held key is planned later in 2026, not day one.
FAQ
Is the Muse AI Agent free?
Yes – with a weekly cap that refreshes. Hit it, then wait or pay. $20 and $100 tiers only raise the token ceiling.
Do I have to connect Gmail on day one?
No. Run a public-web research task or an uploaded file first. You watch the browser and the approval cards without handing over an inbox. One clean success beats five half-connected experiments. When the loop feels sane, add Gmail read-only and tighten from there.
Why did my shopping or form task just stop?
Usually the site blocked the agent, raised a CAPTCHA, or wanted a login Muse does not hold. Open the browser view: it is often waiting on you or reporting refused automated access. Complete the blocked step manually, then continue from the confirmation page. Same pattern as the Amazon-style walls above – manual handoff, not a jailbreak.
Open muse.ai (or the app), lock permissions to ask-first, connect one read-only service, and run the tracker-and-drafts prompt before the day ends. One finished Artifact beats another hour of feature pages.