Usually it is not broken.
An agent that correctly refuses looks exactly like an agent that has failed. It sits there having done nothing, and the instinct is to reinstall which fixes none of the five things most likely to be the cause. Work the ladder in order instead. The first two rungs cost nothing and catch the majority.
Check what is not a fault before you fix anything
Region, then hardware, then account, then permissions reinstall last
Muse launched in the United States only and needs Apple silicon with a current macOS, so two of the commonest “it does not work” reports are simply the product not being available. After that come sign-in and permissions, which between them cover most of the rest. Reinstalling sits near the bottom of the ladder because it changes none of those things.
Scope note: this page is about getting in and getting set up. If Muse runs, signs in and accepts tasks but one went wrong, that is the other page Muse troubleshooting.
Five symptoms that are not faults
Each of these looks like breakage and is the product behaving correctly. None is improved by reinstalling, and two of them are the safeguards you would miss most if they were gone.
The app or a feature simply is not there
Muse launched in the United States only iPhone from September 8, 2026, the Mac from September 17 and integrations roll out region by region on top of that. An absent feature where you are is expected, not broken. The five gates.
It stops just before sending or buying something
That is the confirmation gate, and Meta says it is deliberate. It is also the single safeguard between a draft and an action with no undo, so a version of the app that did not do this would be worse, not better.
It asks you a question halfway through
It has hit a fork your instruction did not settle which folder, whether “last month” includes this week. It cannot invent your preference. Answer it, then put the answer into the task next time. Phrasing a task.
It refuses to touch an area entirely
The area is not granted. This is the one of the five closest to a real problem, and it is still a setting rather than a fault rewording the task will never get past it. How grants work.
It stops accepting tasks late in the week
The weekly allowance is spent. Note that failed runs count too, since the work was performed either way so a few misfires earlier in the week can bring this forward. How the meter works.
If your symptom is on this list, stop here the rest of the page is about faults, and you do not have one.
The ladder, in order
Cheapest and most likely first. Do not skip ahead the later rungs waste time if an earlier one was the answer, and the first two take under a minute between them.
Is the symptom on the list above?
Five of the commonest complaints are the product working. Rule them out before spending effort on anything else.
Time: secondsHas Muse shipped where you are?
United States only at launch. If you are elsewhere, nothing on this page will change that and no workaround exists. Check the gates.
Time: secondsDoes your Mac qualify?
Apple silicon and a current macOS, the same line Meta AI for Mac draws. An Intel Mac will not run it whatever you reinstall. Requirements.
Time: a minuteSign out fully, then back in
More apparent faults dissolve here than at any other rung. Stale browser state and forgotten second accounts are the two usual culprits. Sign-in detail.
Time: two minutesCheck both permission layers
macOS permissions in System Settings under Privacy & Security, and Muse’s own per-area grants inside the app. They are separate, and people routinely check one. The three layers.
Time: two minutesQuit the app fully and reopen it
Permission changes often do not take effect in a running app. Do this before concluding that a grant did not work it is the commonest reason a correct setting looks broken.
Time: secondsOnly now consider reinstalling
And get the installer from Meta rather than anywhere else. A reinstall changes none of rungs two through five, which is why it is last. Getting it safely.
Time: last resort
If you reach the bottom with the problem intact, the useful thing to record before contacting anyone is which rung you were on when it failed that is far more diagnostic than the symptom on its own.
Four ways sign-in goes wrong
Sign-in is where genuine faults cluster, because it involves your browser, your Meta account and the app agreeing with one another three things that can each be in a stale state.
The loop is the signature symptom. You click sign in, the browser opens, you authenticate, the browser says you are done and the app is still sitting on the sign-in screen. Click again and the same thing happens.
A loop is almost never a rejection. It is the app and the browser disagreeing about who just signed in, which is why signing in harder does not help and signing out completely does.
The second most common cause is duller and more embarrassing: a second Meta account you forgot about. The browser is already signed into one identity, the app is expecting another, and the handoff silently completes for the wrong one. Anyone with a personal account and a page or business identity has two, and most people have not thought about which is active in a given browser in years.
Before you start, it is worth checking which account the browser is already signed into. That one observation resolves a surprising share of these, and it costs nothing. The same pattern on Meta AI covers the browser-side detail in full, and it applies here more or less unchanged.
The loop: authenticate, return, still signed out
The browser reports success and the app disagrees. Clicking again simply runs the same disagreement a second time.
Try: sign out on both sides, close the extra browser windows, then sign in once from a single window.
Signed in, but Muse behaves as though you are not
Often the second-account case the handoff completed for an identity that is not the one you meant. Everything then looks subtly empty rather than broken.
Try: check which Meta account the browser is holding before signing in again, not after.
Signed in on the iPhone, not on the Mac
Separate apps, separate releases the iPhone came first on September 8, 2026 and the Mac on September 17 and the Mac has its own hardware requirement on top.
Try: confirm the Mac itself qualifies before treating this as an account problem. Requirements.
Sign-in works but an integration will not connect
Integrations are a separate authorisation from signing in, governed by the service you are connecting, and they roll out region by region.
Try: authorise it from that account’s own settings, and check it is enabled where you are. Integrations.
Setup problems and what fixes them
These are the ones where something is actually wrong. Note how many are resolved by quitting the app rather than by removing it.
| Symptom | Most likely cause | What to do |
|---|---|---|
| Permission granted, still refused | The app was running when you granted it, and has not re-read the setting. | Quit fully not just close the window and reopen.Fixes this most of the time. Try it before anything else. |
| Permission granted in one place, refused anyway | The other layer. macOS permissions and Muse’s per-area grants are separate switches. | Check System Settings under Privacy & Security and the grants inside Muse. The layers. |
| The app will not launch at all | Wrong architecture or an older macOS. Muse needs Apple silicon and a current system. | Check the Mac before troubleshooting the app. Requirements · Intel Macs. |
| Installed, signed in, but nothing works | Usually region rather than installation the app can be present and inert where it has not shipped. | Confirm availability before reinstalling. Where Muse works. |
| Removed the app, integrations still connected | Not a fault and not fixable on your Mac an integration lives in the account that authorised it. | Revoke it in that account’s connected-apps settings. Removing cleanly. |
A note on reinstalling: it is genuinely the right move for a corrupted install, and genuinely useless for region, hardware, account and permission problems which is every row in the table above. Always take the installer from Meta’s own distribution. Why that matters.
Login and setup questions
Why is Muse not showing up on my Mac at all?
The most likely reason by a wide margin is that it has not shipped where you are. Muse launched in the United States only iPhone from September 8, 2026, the Mac from September 17 and Meta has not published an expansion schedule. The gates.
My sign-in keeps sending me back to the browser. What do I do?
Sign out completely, clear the browser state for the sign-in, and try again from a single browser window. A second Meta account you had forgotten about is the other common cause, so check which account the browser already holds before you start. The loop.
I granted a permission but Muse still cannot reach that area.
Quit the app fully and reopen it permission changes often do not take effect in a running app, and this one step resolves a large share of apparent permission failures. Then check the other layer, since macOS permissions and Muse’s per-area grants are separate.
Muse stopped in the middle of a task. Is it broken?
Probably not. An agent hands work back in three situations: a confirmation before something irreversible, a question it cannot answer for you, and a wall such as an ungranted area. Only the third is close to a fault, and even that is a setting. The taxonomy.
Does a failed run still use up my weekly allowance?
Assume it does, since the work was performed either way. That is why reading the plan before a run matters more than inspecting the result after one. How the meter works.
Will reinstalling fix it?
Rarely, and it is near the bottom of the ladder for a reason. Reinstalling does not change your region, your Mac’s hardware, your account, your permissions or your allowance which between them account for most problems. The order.
Does uninstalling remove the account integrations I authorised?
No. An integration such as Instagram, Facebook or Google Workspace lives in that account, not on your Mac, and stays authorised until you revoke it there. Removing cleanly.
Muse runs but an integration is missing. Why?
Integrations roll out per area and per region, so the agent can be present while a particular connection is not yet enabled where you are. That is not a fault and no reinstall will produce it. Which exist.
Why does Muse work on my iPhone but not my Mac?
They are separate apps with separate releases iPhone on September 8, 2026, Mac on September 17 and the Mac has its own hardware requirement of Apple silicon and a current macOS. Check yours.
What is the difference between this page and the Muse troubleshooting page?
This page covers getting in and getting set up: region, hardware, sign-in, permissions and integrations. Muse troubleshooting covers the app once it is running and a task has gone wrong.
Work the ladder before you reach for the installer.
Five of the commonest complaints are the product working correctly, and two more are settings. Reinstalling touches none of them.
Independent guide not affiliated with Meta. Behaviour described as of September 2026; statements about confirmation prompts are Meta’s own, and the installer should only ever come from Meta’s own distribution.