THE MUSE BUNDLE · FOLLOW-ALONG GUIDE

Implementation Manual

For what to buy, see the Muse Bundle checklist; for how to actually set it all up, step by step, read this manual. Muse does most of the work for you — you only step in at the few moments that require you personally. Every step includes "what you do", a ready-to-copy prompt, and a way to verify the result. Just follow along.

Parts of the prompts highlighted like [this] are placeholders: replace them with your own details before copying and sending the whole prompt.

Part 1: First, understand what Muse can do for you

Many beginners assume Muse is like an ordinary chat AI — it can answer questions and give advice, but the actual doing is still on you. That is not the case. Muse is an AI assistant with its own working environment, and working with it rests on four key abilities. Get these straight and every step after will make sense.

1. It has its own computer in the cloud

Every Muse account comes with a dedicated cloud computer (think of it as a computer in the cloud that is always on). On it, Muse can actually carry out operations: search the web, open pages, download and process files, run programs. It doesn't just tell you how — it does the thing and shows you the result.

2. It can operate a browser and register accounts, like a person would

This is the most important point for setting up the bundle: registering Gmail and ChatGPT, buying the domain and the host — you don't have to click through these websites yourself. Muse can do it for you in the browser on its computer. It opens the sign-up page, fills in the fields one by one, clicks Next, and works through the settings pages. It is exactly like doing it yourself on a web page — except the hands aren't yours.

3. When a step needs you personally, it hands the browser back to you

Some steps a machine cannot do; they need you in person. When one comes up, Muse stops and gives you control of the same browser window. This is called "taking over the browser": the page stays right where it was, you complete that one step (typing the code sent to your phone, tapping the human verification, confirming a payment), tell Muse you're done, and it continues from exactly that spot. No logging in again, no starting over.

Only four kinds of steps need you personally. Remember these four:

StepWhy it has to be you
Verification codes (SMS, email)Codes are sent to your phone and your inbox; only you can see them
Human verification (CAPTCHA, liveness checks)The site needs to confirm a real person is operating
Payment confirmationThe money leaves your card; you must confirm it yourself
Real-name informationID documents and real-name details can only be provided and submitted by you

Everything else — filling forms, changing settings, ticking boxes, waiting, checking — Muse does it all.

4. It can connect to your Gmail and Google Drive

With your authorization (one click to agree), Muse can read your Gmail and use your Google Drive to store and fetch files. Website backups going into your Drive, and Muse keeping an eye on important mail, both rely on this. Note: you choose which Google account gets connected at the authorization step — that is separate from which email the Muse account itself was registered with.

Two more things worth knowing: it remembers — your preferences, your progress, your account setup carry across conversations, so you don't re-introduce everything each time. And it can work on a schedule — for example, updating your website every day and pushing the result to your Muse app, where you see it on your phone.

What it cannot do (set expectations early)

  • It can't receive your text messages or see your email verification codes (unless you have authorized it to read that mailbox — and by our house rules, sign-in codes never go through it).
  • It can't pay for you, and it can't pass human or liveness verification.
  • It doesn't know any of your passwords. When a step needs a password typed (say, setting a new account's password), it asks you to take over; you type it and save it yourself.

Part 2: Two starting points — which path are you on?

The destination is the same for everyone: one Gmail master account tying together Muse, Gemini Pro and ChatGPT, plus a domain, a host, a website and a proxy node. But there are two starting points:

Path 2 (the simple case): your Muse account was registered with a Gmail address in the first place. The foundation is already right — start at Step 0 of Part 4, "The shared steps", and let this Muse set up the rest.

Path 1 (one account swap needed): your Muse account was registered with a different email, or it's a ready-made account you bought. Such an account serves only as a "bootstrap":

  1. Use it first to register a Gmail account for you (it works the browser; you take over for codes and the like);
  2. Once you have the Gmail, register a new Muse account with that Gmail;
  3. Hand the work over to the new account, which completes the rest of the bundle;
  4. The old account is then retired — or kept as a spare.

This little detour leaves you with a clean bundle — "one Gmail ties everything together" — with no awkward account relationships. Path 1's three preliminary steps are in Part 3; after them you join the shared steps.

If you bought a ready-made account, do one extra thing before starting: have the bootstrap Muse walk you through changing the account password and checking its security settings (signed-in devices, recovery options), so the account is fully under your control, before you register the Gmail. Also, the email attached to a bought account belongs to the seller — never use it as the recovery email for anything important.

Part 3: Path 1's three preliminary steps (Path 2 skips this part)

P-1 The opening prompt for the bootstrap Muse

Copy this to Muse

I'm new to AI, and I'm setting up the full configuration in the "Muse Bundle" guide: https://muse.zhudong.net/en/bundle/

My situation: this Muse account is [registered with a non-Gmail email / a ready-made account I bought — pick one], and it serves only as a bootstrap. Please help me complete three things first: (1) (if it's a bought account) walk me through changing the password and checking the security settings; (2) use your browser to register a Gmail account for me, which will be my master account from now on — during registration, whenever a step needs me personally (phone verification codes, human verification, setting the password), stop and let me take over the browser, and continue when I'm done; (3) once the Gmail is registered, guide me to register a new Muse account with that Gmail, and hand over the bundle's progress and house rules to it. After that, this account will be retired (or kept as a spare). First, repeat this plan back to me to confirm you understand it.

Verify: its summary matches the above; for a bought account, it should first walk you through the password change and security check.

P-2 Registering Gmail (Muse does the work; you take over at three points)

This step has no separate prompt — P-1's instructions already cover it. You personally appear at just three points; know them in advance:

  1. Setting the password: take over and type a strong password yourself, and save it right away (a password manager, or written down offline). Muse does not keep your Gmail password.
  2. Phone verification: take over, enter your phone number, and type the SMS code.
  3. After registration: have it walk you through turning on two-step verification — it opens the settings pages and guides you to the right spot; scanning the code and entering verification codes is yours to do. Save the backup codes safely.

Verify: the new Gmail signs in normally; two-step verification is on; the password and backup codes are in your hands.

P-3 Register the new Muse and hand over

With the Gmail ready, register a new account at muse.ai using that Gmail (the bootstrap Muse can keep driving the browser through the sign-up pages; you take over when the Google authorization sign-in appears). Then open the new account's Muse and send it this handover prompt:

Copy this to the new account's Muse

Hi, I'm [your name or handle]. I'm setting up the full configuration in the "Muse Bundle" guide: https://muse.zhudong.net/en/bundle/

My master Gmail account is [your Gmail address] (it's the one you were registered with), and from now on it ties everything together: Gemini Pro, Drive, ChatGPT, and the registration and recovery of the domain and host all use it. The previous bootstrap account has already registered this Gmail for me; from here you take over and complete all the remaining steps: activating Gemini Pro and setting up Drive, registering ChatGPT, buying the domain, choosing and initializing the host, deploying the proxy node, testing streaming, building the personal website, and a final review that produces my configuration record.

House rules first: for registrations, please use your browser and do them for me; when a step needs me personally — verification codes, human verification, payments, real-name information — ask me to take over the browser. The technical work is yours. Report after each step and wait for my confirmation before continuing. For anything that costs money, give me the options and current prices first; I decide, then you act. Never ask me for my Gmail password or verification codes.

First, repeat back to me: what the bundle consists of, which steps remain, and who is responsible for each.

Verify: the new Muse's summary is correct. From here on, you talk to the new Muse; the bootstrap account can be retired.

Part 4: The shared steps (both paths)

Step 0: Opening — set the house rules with the Muse in charge

Path 2 readers: send the prompt below to your Muse — it's the first message of the whole process. Path 1 readers: you already covered this in the handover prompt; skip this step.

Copy this to Muse

I'm new to AI. I want to set up the full configuration in this "Muse Bundle" guide in one go: https://muse.zhudong.net/en/bundle/

Please read it through, then we'll go step by step. The division of labor, up front: for registrations, please use your browser and do them for me; when a step needs me personally — verification codes, human verification, payment confirmation, real-name information — stop and let me take over the browser, and continue when I'm done. All other technical work is yours. After each step, report the result to me and wait for my confirmation before moving on. For anything that costs money (which host to pick, whether to buy a residential IP), give me the options and current prices first; I decide, then you act. I won't give my Gmail password or sign-in codes to anyone, and you shouldn't ask me for them. First, repeat back to me: what the bundle consists of, how many steps there are in total, and who is responsible for each step.

Verify: its summary of the parts and steps matches the guide, and the division of labor is right. Then proceed.

Step 1: The master Gmail — security settings and connecting it

What you do: Path 2 readers, your Gmail is the one you registered Muse with — you already have it. Path 1 readers, your Gmail was just registered in the preliminary steps. Both paths do the same thing here: lock it down, and connect it to Muse.

  1. Turn on two-step verification (if it isn't already): have Muse open the Google Account security settings and walk you through it; scanning and entering codes is yours. Save the backup codes.
  2. Authorization: Muse starts the Gmail and Google Drive connection; you confirm on the authorization page — double-check you're authorizing the master Gmail account, not a different one.
Copy this to Muse

My master Gmail account is [your Gmail address]. Please walk me through two things: (1) check whether two-step verification is on for this account, and if not, open the settings page and help me turn it on; (2) start the Gmail and Google Drive connection authorization — I'll do the confirming. Once connected, prove it to me: read me the subject of the newest email in my inbox, and create a folder in Drive called "Website Backups" — all website backups go there from now on. Finally, remember this: this Gmail is the master account for all my services; for anything account-related, it's the source of truth.

Verify: two-step verification is on; both proof actions (reading the email subject, creating the folder) succeed; Muse appears in your Google Account's third-party access list.

Step 2: Activate Gemini Pro

What you do: you complete the subscription payment yourself (Muse can drive up to the payment page; you take over to confirm payment).

Copy this to Muse

Please use your browser to walk me through subscribing to Gemini Pro (Google AI Pro), using my master Gmail account. Stop at the payment confirmation step and let me take over; after I've paid, confirm the activation, and tell me: how much total Google Drive storage do I have now? That settles both Drive capacity and website backups.

Verify: Gemini works with the Pro model; Drive storage matches the subscription.

Step 3: Register a free ChatGPT account

Copy this to Muse

Please use your browser to register a free ChatGPT account for me, with my master Gmail. If an email verification code or human verification appears, let me take over. Registration is all I need — no paid upgrade.

Verify: ChatGPT signs in with the master Gmail. All three AI accounts are now in place.

Step 4: Buy the domain

What you do: first have Muse find names and check prices; at the end, you take over at Cloudflare to confirm the purchase.

Copy this to Muse (finding a name)

I want to buy a .com domain for my personal website, on Cloudflare. My name/handle is [fill in], and the site will mainly be for [fill in, e.g. blogging / showing my work]. Please give me 10 candidate domains that are short, memorable and easy to spell, and check each one: is it available, the first-year price, and the renewal price. No hyphens or numbers, and no premium-priced domains.

Copy this to Muse (buying and configuring)

I'll take [the domain you chose]. Please use your browser to walk me through buying it on Cloudflare: register the Cloudflare account with my master Gmail, and stop at payment confirmation so I can take over. After the purchase, set these up as well: turn on auto-renew, turn on WHOIS privacy protection, and set up Cloudflare Email Routing so mail to contact@[domain] forwards to my master Gmail. When it's all done, report the status of each item.

Verify: the domain shows as active in Cloudflare with auto-renew ON; send a test email to contact@your-domain and confirm it arrives in Gmail.

Step 5: Buy the host

What you do: Muse checks prices and helps you choose; you decide; it walks you through checkout; you take over for payment.

Copy this to Muse

Help me choose a host using the two tiers in the Muse Bundle guide. My situation: budget [pick one: budget tier at $5–$6/month / comfort tier at $10–$12/month]; main uses are a personal website plus a proxy node for my own use; I'll be connecting from China. First, check the current prices and US West Coast availability (Los Angeles / Seattle / Silicon Valley / San Francisco) on each provider's official site: for the budget tier, Vultr, Linode and DigitalOcean; for the comfort tier, DMIT (route priority) and the majors' 2GB plans (specs priority). Put the results in a table for me. Once I pick one, use your browser to walk me through ordering (region, Ubuntu LTS as the OS, the plan I chose), and stop at payment confirmation so I can take over. After the order succeeds, organize the host's IP address and initial login details for me to save.

Verify: the order confirmation email (sent to your master Gmail) has arrived; the IP address and initial login details are in your hands.

Step 6: Hand the host to Muse — initialization and hardening

Copy this to Muse

My host is ready. IP: [IP address], OS: Ubuntu, initial login username and password: [fill in]. Please complete the initialization and report item by item:

1. Log in to the host and update the system to the latest;
2. Create an everyday admin account and set up SSH key login; once key login is confirmed working, disable password login and direct root login;
3. Turn on the firewall, allowing only SSH, the website ports (80/443) and the ports the proxy will need later;
4. Set the timezone and automatic security updates;
5. Finally, give me an initialization report: what was changed, how I log in from now on, and whether the initial password is now useless.

Note: this is your own Muse and your own host, so the initial password may be given to it; once key login is configured, that password is retired.

Verify: the report is complete; have it demonstrate live that the new login works and the old password no longer does.

Step 7: Deploy the proxy node and get your subscription link

Copy this to Muse

Deploy a proxy node on this host, using the bundle's standard setup: sing-box as the server, with the Hysteria2 + VLESS Reality protocols. When it's done, deliver:

1. A subscription link — you host and maintain it; if nodes ever change, you update the server side and I just refresh the subscription;
2. Step-by-step instructions for importing the subscription in Clash (computer), Shadowrocket (iPhone) and v2rayN (Windows);
3. How to test speed and switch nodes after importing.

The deployment must not interfere with the website service we'll install later; show me the port plan first.

Verify: the subscription imports successfully on phone and computer; you can open a US website and confirm your exit IP is in the US.

Step 8: Test streaming; if it fails, add a residential IP

Copy this to Muse

Please test, one service at a time, whether this host's IP can watch US streaming: Netflix, HBO, Disney+ and Prime Video. Report each result separately: works / doesn't work, full unlock or partial. Don't give me a vague "should be fine".

If it fails, send this one:

Copy this to Muse (if streaming fails)

The host's IP can't stream. Handle it the bundle's fallback way: keep the host — no refunds — and buy a separate US residential IP as the dedicated streaming exit. First give me options and prices: IPRoyal (which lets me rent a single IP short-term to test), WebShare, ResIP and the like, explaining which are shared vs. dedicated and how traffic is billed. Once I choose, use your browser to walk me through the purchase (I'll take over for payment), then configure the residential IP as the streaming-only exit (only streaming traffic goes through it; everything else goes direct via the host), and re-test every service for me.

Verify: each of the four services has a clear verdict; if you added a residential IP, the re-test must pass before this step counts as done.

Step 9: Build the personal website (pick one route)

Copy this to Muse (Route A: WordPress)

Build my personal website on my domain [your domain], the WordPress route: you install WordPress, pick a clean theme, install the common plugins, enable HTTPS, create the Home, About and Contact pages, and put the domain email contact@[domain] on the Contact page. When the admin account is ready, hand me the login details, and turn on automatic backups: site files and database backed up regularly to the "Website Backups" folder in my Google Drive. When you're done, give me a summary: the site URL, the admin URL, how often backups run, and how I ask you for redesigns or new features later.

Copy this to Muse (Route B: custom-built)

Custom-build a personal website for me on my domain [your domain]. Here's my idea: [what the site is for, which pages you want, what style you like, and any reference sites]. First, give me a plan and page structure based on my description for me to approve; only start building after I approve. Requirements: HTTPS on; Home, About and Contact pages; site files and data backed up regularly to the "Website Backups" folder in my Google Drive; later, for redesigns and new features, I'll just give you instructions — you make the updates and push the results to my Muse app for me to see.

Content updates (for everyday use later):

Copy this to Muse (when updating the site)

Please update my website: this time the topic is [fill in], and the material is [fill in: paste text / attach a file / give a link]. Show me a draft first; publish only after I approve, and push a notification to my Muse app once it's live.

Verify: the domain opens the site with no certificate warnings; a backup is visible in Drive's "Website Backups"; the layout looks right on your phone.

Step 10: Final review — have Muse produce your configuration record

Copy this to Muse

The bundle should now be fully set up. Please review everything item by item and give me a "My Configuration Record": (1) what each of the three AI accounts signs in with; (2) where the domain was bought and when it renews; (3) which host provider and plan, how much per month, and how to log in; (4) where the proxy subscription link is and how to refresh it; (5) the four streaming test results, and whether a residential IP is in use; (6) the website URL and admin URL, where backups live, and when the most recent backup ran. Facts only in the record — no passwords or keys of any kind. If I ever change phones or computers, this record alone should let me restore everything.

Verify: every item in the record matches reality; keep a copy for yourself.

Part 5: Everyday prompts (keep these handy)

  • Health check: "Please check the health of my whole bundle: how much traffic and disk the host has left, whether the website opens, how many days until the certificate expires, and when the most recent backup ran — give me a checklist."
  • Node trouble: "My proxy stopped connecting. Please check the server side, and once it's fixed, tell me what caused it and what you did."
  • Renewal reminders: "List everything I need to renew — domain, host, Gemini Pro, residential IP — with each expiry date and amount, and remind me a week ahead."
  • Editing the site: "Please change [which page]'s [which content] to [new content] on my website, and push the result to me when it's done."

Part 6: Security reminders (once more, to close)

  1. Gmail is the master key: keep its password yourself, always keep two-step verification on, and store backup codes offline.
  2. Codes and passwords never go through Muse: sign-in codes and account passwords are typed by you, when you take over the browser — never sent in chat to anyone, including people claiming to be support staff.
  3. Payments are always confirmed by you: Muse can drive right up to the payment page; the final tap must be your finger.
  4. Bought accounts: change the password first: before a bought account is used to register or bind anything important, change its password and review its security settings.
  5. The host's initial password dies after setup: once Step 6 is done it should no longer work; the configuration record deliberately contains no passwords.

Haven't seen the checklist yet? Back to the Muse Bundle →

Invitation code copied