Muse can make it. It cannot hand it to anyone.

What Muse is, in the part that matters here

Meta launched Muse on 8 September 2026. Reading past the announcement, three details decide whether a hosting service can be useful to it, and all three are in Meta's own description.

• It has a real computer. Each Muse runs on a persistent, isolated Linux VM with a full browser and enough storage, CPU and memory to do the things you would do on your own machine. It is not a chat window with a retrieval tool bolted on.
• It writes its own tools. Meta's line is blunt: if a task needs a tool that does not exist, your agent builds it for you. An agent that can write a tool can write an HTTP request.
• It lives in WhatsApp. You talk to it in the Muse app or directly in WhatsApp, which means the output of most tasks needs to end up in a chat thread with other people in it.

Put those together and the gap is obvious. Muse can research, draft, analyse and decide. The moment the result has to reach a person who is not in the conversation, it has nothing to reach for.

Why there is nothing to install

There is no Muse plugin for Stacktree, and there is no plugin for anything else either: Meta has not opened a third-party connector programme. That would be a problem if integrations were the only way in. They are not.

Stacktree's first publish is anonymous by design. One HTTP request, no key, no account, no signup step for the agent to get stuck on:

curl -X POST https://api.stacktr.ee/sites -F file=@page.html

That returns the live URL, the page id, an expiry and a claim token. It is the same route Grok Bot takes, and Grok Bot reached it unattended, on the first attempt, from a single sentence of instruction. The thing standing between an agent and a service was never whether an integration existed. It is whether the first useful action can be completed without an account.

The WhatsApp part is the whole point

Most agent-hosting arguments are about the agent. This one is about the recipient.

Muse is used in WhatsApp, so its output lands in a thread with other people in it. A chat app treats a link and a file as different species. A Stacktree link unfurls into a card carrying the page title, a description and a preview image, and opens in the browser the recipient already has, on the phone they are already holding. A file attachment shows a filename, needs downloading, opens in whatever app happens to claim the extension, and is stale the second the agent revises anything.

The revision case is the one that actually bites. Ask Muse to change something and a file has to be sent again, so the thread now holds two versions and the person reading it has to work out which is current. A published page is replaced at the same address: the link from an hour ago shows the new version, and there is only ever one of it.

Say this, not that

Two instructions that make the difference between a link you can use and one you cannot:

• Ask for the page and the link together. "Write that up as an HTML page and publish it to Stacktree so I can send it." Asking for a document first and a link afterwards usually gets you a file.
• Ask for revisions in place. "Update the page you already published" rather than "publish an updated version". The anonymous publish hands the agent a claim token that works as a keyless update credential, so the same URL can be replaced up to thirty times an hour with no account involved. Without that instruction you get a second link.

If the page is for a client rather than for you, say so, and put it on a paid plan: the page then sits on your own domain behind a passcode, and everything published for that client collects at one address.

What we tested

We ran it by hand on 8 September 2026, launch day, and Muse published to Stacktree when asked. That is the claim, and it is the only one we are making about Muse's behaviour.

Verified independently on our side, and checkable by anyone: the anonymous publish path works with no key and returns a keyless update credential, a published page unfurls correctly for WhatsApp's crawler, and Meta's agents are named in our robots rules and are not blocked at our edge.

If you run it and get something different, including a failure, tell us and we will write down what happened.

Keeping the link alive

An anonymous page lasts 24 hours. That is deliberate: it makes the first publish free of any signup, and it is long enough to prove the thing works. It is not long enough for anything you have sent to a client.

Claiming the page into an account removes the expiry and moves the credential into the account, after which the agent updates through an API key instead of the claim token. The free plan keeps 3 pages for 7 days each. Paid plans from $19 a month remove the expiry, add passcodes and email-domain gates, and put pages on your own domain.

Other assistants

If you also use a coding agent, it has a faster path than browser automation. Claude Code, Codex CLI, Cursor and Claude.ai connectors speak MCP and call publish_html directly. One command sets them all up:

npx stacktree-install

See every agent integration for the full list, or hand any agent that can fetch a URL the setup instructions at stacktr.ee/prompt.md, which now branches on whether the agent can install anything at all.