Is Muse only for personal use?

No. It is marketed that way, but the same browser that books restaurants also works in GitHub, your hosting dashboard, and a domain registrar. The builder jobs above are the same skill applied to a different task.

How does Muse connect to GitHub if there is no connector?

Two ways. The official GitHub connector in Muse → Connectors for read-only browsing of repos, issues and pull requests. For anything else, open github.com in Muse’s browser, log in yourself, and instruct Muse to work in that session — it never sees your password.

Can Muse deploy my site?

It can run the deploy steps in your browser session — clone, build, configure — but the prompts above keep the gate: show the plan first and wait for your OK. Never let an agent push to production without you reading the approval card.

Can Muse buy a domain for me?

It can search availability and compare prices, and it can complete the purchase in your registrar session — but only after you approve the exact domain, price, and registrar on the approval card. Premium domains are where the surprises live; the prompt flags them.

There is a free tier at 100M tokens a week, Power at $20 a month for 500M a week, and Maximum at $100 a month for 3B a week, according to Meta’s Help Center. Builder work is token-heavy — browsing dashboards is the expensive part — so start on free and watch the meter before you upgrade.

Is it safe to let Muse into my GitHub and hosting?

With the same discipline you would use for anyone with your laptop: log in yourself, start read-only, scope to the repo or site the task needs, and approve every write, spend, or public change. Revoke by signing out or removing the session in the provider’s account page. See our safety guide for the details.

Muse for builders: domains, GitHub, hosting, plans

For founders and one-person teams · ~30 min to set up · Needs: a login you do yourself

Muse is marketed as a personal assistant, and most people use it that way. But it runs on its own browser, and once you log in to your own accounts in that browser, it can work in them the way you would — searching domains, triaging repos, checking your hosting bill, researching a market, drafting a plan. This page covers the builder stack: the stuff that gets an idea from a name to a live site.

The pattern that makes it safe is the same one that powers everything else on this site: you log in, Muse works, you approve. You type the password once in Muse’s browser; after that Muse can navigate, read, summarize, and draft — and every send, spend, or public change still waits for your approval card. That split is what keeps the work fast and the credentials yours.

This is an independent guide, not a Meta site. If you are after the shop-owner side of business — scheduling, invoicing, inbox — see Muse for small business.

The login pattern · read this first

There is no "connect Cloudflare" magic button for every service. The reliable way is to open the site in Muse’s browser, log in yourself (including any two-factor prompt — never paste codes into chat), and then instruct Muse to work in that session. Muse never sees your password; it drives the browser you signed into. Revoke by signing out, or remove the session from the provider’s account page. Details on the custom connector guide →.

The builder jobs

Do them in this order: name, code, hosting, then the plan that ties it together.

Job 01

Find a domain name

Muse checks availability, flags premium pricing (the hidden tax on good names), and suggests alternatives you would not have thought to type. It does not buy — you approve the purchase in the registrar.

Try this prompt (example)

Check domain availability for [idea] across .com, .app, and .co — flag what's taken, what's premium priced, and suggest 10 alternatives that are available and under $30. Don't buy anything yet.

Job 02

Open your GitHub in Muse’s browser

Open github.com in Muse’s browser, log in yourself, and Muse can triage your repos, summarize pull requests, and list stale issues — all read-only first. For the connector route and permissions, see GitHub × Muse →.

Try this prompt (example)

Go to my GitHub in your browser (I'll log in first), then: list my repos sorted by most recently pushed, find ones with open issues older than 30 days, and summarize each in one line. Read-only — don't change anything.

Job 03

Audit your hosting

Log in to your provider in Muse’s browser and ask for the full inventory: sites, plans, renewal dates, monthly cost. The renewal list alone is worth the prompt — nobody checks it until something lapses.

Try this prompt (example)

In my [hosting provider] dashboard (I'll log in first), list my sites with their plan, renewal date, and monthly cost. Note anything expiring in the next 90 days. Read-only.

Job 04

Deploy, but on your approval

Muse can walk a deploy end-to-end — clone, build, configure, push — but the prompt keeps the gate: show the plan and wait. That is the difference between a deployment and a surprise.

Try this prompt (example)

Walk me through commissioning [project]: clone the repo, check it builds, and show me what's needed to deploy it to [hosting]. Don't deploy yet — show me the plan first and wait for my OK.

Job 05

Research the market

Who sells it, what they charge, who is underserved. Muse browses and summarizes; you check the sources it cites before you act on anything.

Try this prompt (example)

Research the market for [product/service] in [region]: who sells it, what they charge, who's underserved, and where the gaps are. Cite sources. Show me before you recommend anything.

Job 06

Write the business plan

One page, 300 words, plain English. The output is a starting point for a real conversation with a cofounder or a bank — not a document to file and forget.

Try this prompt (example)

Draft a 1-page business plan for [idea]: who it's for, what problem it solves, how it makes money, and the first 3 steps to launch. Keep it under 300 words, plain English.

Job 07

Write the sales strategy

Three channels, the hook, and a two-week test that proves demand before you spend on ads. The test plan is the part most people skip and the part that matters.

Try this prompt (example)

Write a sales strategy for [product/service] targeting [audience]: 3 channels to reach them, the message that hooks them, and a 2-week test plan to prove demand before spending on ads.

One rule that matters

Muse driving your own browser is powerful because it is fast and it reads everything. Keep the boundary: read and draft freely, write and spend only with your approval. Code can carry secrets, hosting changes can break production, and plans can commit you to spend — all of those wait for your yes. More detail: is Meta Muse safe? →

How to start

Search domains first — about 10 minutes. Run Job 01 and pick a name before anything else. The name drives the repo, the hosting, and the plan.
Log in in Muse’s browser and inventory — about 20 minutes. Jobs 02 and 03, read-only. You get a full map of what you own and what renews when.
Research, then draft — one sitting. Jobs 05 to 07 turn the inventory into a plan. Do not deploy (Job 04) until the plan exists.

Want a hand?

Want someone to set this up with you? Book a 1:1 setup call → — we walk through connectors, approval rules and your first prompt on a screen share. Not what you were after? Back to for businesses →

Next step

Name, code, hosting, then plan.

If you would rather have it set up with you — two or three apps connected read-only, permissions tightened, three prompts that work — book a 30-minute screen share. You do the clicking; we never take your logins.

Start the 10-minute path →Book a 30-min setup

Paste YW21RI at signup or in Muse Settings. No card needed to start, and nothing is bought or sent without your approval.

Related: All business setup options

Muse for builders: questions

Is Muse only for personal use?: No. It is marketed that way, but the same browser that books restaurants also works in GitHub, your hosting dashboard, and a domain registrar. The builder jobs above are the same skill applied to a different task.
How does Muse connect to GitHub if there is no connector?: Two ways. The official GitHub connector in Muse → Connectors for read-only browsing of repos, issues and pull requests. For anything else, open github.com in Muse’s browser, log in yourself, and instruct Muse to work in that session — it never sees your password.
Can Muse deploy my site?: It can run the deploy steps in your browser session — clone, build, configure — but the prompts above keep the gate: show the plan first and wait for your OK. Never let an agent push to production without you reading the approval card.
Can Muse buy a domain for me?: It can search availability and compare prices, and it can complete the purchase in your registrar session — but only after you approve the exact domain, price, and registrar on the approval card. Premium domains are where the surprises live; the prompt flags them.
What does it cost?: There is a free tier at 100M tokens a week, Power at $20 a month for 500M a week, and Maximum at $100 a month for 3B a week, according to Meta’s Help Center. Builder work is token-heavy — browsing dashboards is the expensive part — so start on free and watch the meter before you upgrade.
Is it safe to let Muse into my GitHub and hosting?: With the same discipline you would use for anyone with your laptop: log in yourself, start read-only, scope to the repo or site the task needs, and approve every write, spend, or public change. Revoke by signing out or removing the session in the provider’s account page. See our safety guide for the details.