# Muse4AI — full guide (English) Source: https://muse4ai.andrewbabo.com/docs # What is Muse4AI? Learn how Muse4AI connects your Windows PC, your Muse account, and AI agents, and what using it means for your usage limit. Source: https://muse4ai.andrewbabo.com/docs/what-is-muse4ai · Updated 2026-11-02 ## Before you start - Have access to a Windows PC. - Have your own Muse account if you want to create results. ## 1. Understand the bridge Muse4AI is a free Windows app that runs on your PC and works with your own Muse account. You can send requests in Studio or let AI agents send them through MCP or REST. It is not a new AI model and is not affiliated with Meta. Creating images and videos uses your Muse account's usage limit; the app itself is free. ## 2. See where work is tracked Queue brings jobs together so you can follow their status and open their results. Finished files appear in Library and are saved on your PC. ## 3. Choose your starting point Start with [installation](https://muse4ai.andrewbabo.com/docs/install), then [add a Muse account](https://muse4ai.andrewbabo.com/docs/add-muse-account). You can try Studio before following [Connect an agent](https://muse4ai.andrewbabo.com/docs/connect-overview). Agent access needs an API key. ## Check it worked You know which account supplies the results, where the files are saved, and whether to start in Studio or connect an agent. ## If it doesn't work ### Do I need a separate Muse4AI account? No. There is no separate Muse4AI account. You sign in to your own Muse account inside the app. ### Why did creation stop if the app is free? Muse controls your account's usage limit and availability. The app pauses when Muse reports a limit, verification request, or unsupported region; it does not bypass these checks. --- # Install Muse4AI Install Muse4AI with the Windows EXE or ZIP package, handle SmartScreen safely, and keep your data when updating. Source: https://muse4ai.andrewbabo.com/docs/install · Updated 2026-11-02 ## Before you start - Use Windows 10 or 11, 64-bit. - Have the Muse4AI EXE installer or ZIP package from a source you trust. - If updating with the EXE, you can leave the app open: setup closes it the normal way, like choosing Quit. With the ZIP, right-click the tray icon and choose Quit first; the window's X only minimizes it to the tray. ## 1. Choose EXE or ZIP For the simplest route, open the EXE installer, choose English or Tiếng Việt, and follow its instructions. For ZIP installation, extract the whole package into a folder first. ## 2. Check any Windows warning The app is not code-signed, so SmartScreen may warn you. Only if you trust the package, choose **More info → Run anyway**. Do not continue with a package whose checksum check fails. ## 3. Run PowerShell if using ZIP Skip this step if you used the EXE. In the extracted folder, type `powershell` in File Explorer's address bar and press Enter. Run the command below. It does not change the machine's saved execution policy. ```powershell powershell -ExecutionPolicy Bypass -File .\install.ps1 ``` ## 4. Check the install and data locations The app installs to `%LOCALAPPDATA%\Programs\Muse4AI`. Its data stays in `%APPDATA%\MuseStudio` when you install an update, including accounts, settings, queue, and library records. Downloaded results use the library folder you choose. ## 5. Continue with first-run setup The installer opens the app. If this is your first installation, follow the welcome setup in [First open](https://muse4ai.andrewbabo.com/docs/first-open). ## Check it worked Muse4AI opens from its shortcut. A first installation shows the welcome setup; an update keeps your existing data. ## If it doesn't work ### The installer says the app is still running. What now? The EXE asks the app to quit and waits about 45 seconds. If jobs are still running, Muse4AI first asks whether to quit. Answer it or let the jobs finish, quit from the tray icon (not the window's X button), then run the installer again. ### The package does not match its checksums. Should I continue? No. The package may be damaged or modified. Download a fresh copy from a trusted source. ### The new version will not open. What can I do? See [Updates and backups](https://muse4ai.andrewbabo.com/docs/updates-and-backups) before rolling back. Older versions may not read data upgraded by a newer version. --- # First open Complete first-run setup, choose where results are saved, and prepare a Muse account before sending your first request. Source: https://muse4ai.andrewbabo.com/docs/first-open · Updated 2026-11-02 ## Before you start - Install Muse4AI and open it. - Choose a local folder with space for downloaded results. - Have your Muse sign-in details and a working proxy ready if you want to finish account setup now. ## 1. Read the notice Read the account-risk notice, then acknowledge it and choose Continue if you agree. Muse can limit or suspend accounts; the app stops for verification, usage limits, or unsupported regions. ## 2. Choose the results folder Keep the suggested folder or choose another folder, then confirm it. Images and videos are organized by month and batch. ## 3. Prepare a proxy and account Add a working proxy, then add your Muse account and sign in in its separate window. You can skip setup, but jobs cannot run until an account is ready. See [Add a Muse account](https://muse4ai.andrewbabo.com/docs/add-muse-account). ## 4. Enter Studio and check your preferences Enter Studio when setup is complete. In Settings › General, choose your language and check the library folder. Changing the folder affects new files only; old files remain where they are. App data is separate, in `%APPDATA%\MuseStudio`. ## Check it worked Studio opens, your language is correct, and your chosen library folder is shown in General settings. ## If it doesn't work ### I skipped account setup. Can I return to it? Yes. Open Accounts and add an account when your proxy and Muse sign-in details are ready. ### Why did changing the folder not move my old files? The setting changes where new results are saved. It does not move existing files. --- # Add a Muse account Add a Muse account with a proxy, sign in yourself, and check that the account is ready to accept jobs. Source: https://muse4ai.andrewbabo.com/docs/add-muse-account · Updated 2026-11-04 ## Before you start - Open Muse4AI and finish the first-run notice. - Have access to your Muse account and its verification method. A secondary account is recommended. - Have a working proxy. A separate proxy for each account is best; accounts can share one, but then they go out through the same IP address. ## 1. Open the account dialog Open Accounts and choose Add account. Enter a recognizable alias; it is a label in the app, not your Muse login. ## 2. Assign a proxy Each proxy in the list shows “Not in use” or which accounts already use it, unused ones first. The app pre-selects an unused healthy proxy; to share one, click it and read the short note. If there is no healthy proxy, import and test one first. A proxy failure stops every account on it; the app does not switch to a direct connection. ## 3. Sign in yourself Continue to sign-in. In the separate Muse window, enter your account details and complete Muse's verification yourself. If Muse opens another page (for example Meta Accounts Center or a tool's Connect button), it shows in its own small window or a tab, through the same proxy. The app does not store passwords or verification codes. ## 4. Check that the account is ready The app detects a completed sign-in automatically. Return to Accounts and check the account's status before sending a Studio request. Resolve any verification or usage-limit notice first. ## Check it worked The account appears in Accounts without a sign-in or proxy error and is ready to accept work. ## If it doesn't work ### Every proxy is already in use. What should I do? You can pick one and share it — the list shows who already uses it. For separate IP addresses, open Settings › Proxy to add and test another proxy. ### I clicked Connect (or opened Meta Accounts Center) and a new page appeared. Where is it? A small sign-in window opens over the Muse window and closes itself when you finish. Other pages open in one extra window; with two or more pages, a thin row of tabs appears at the top (Ctrl+W closes a tab, Ctrl+Tab switches). They only open while you use the account's window, always through its proxy. ### Muse asks for verification. Can the app finish it? No. Open the account's control window and complete the check yourself. When finished, use the session-check action if shown. Stop if Muse reports an unsupported region or unusual account restrictions. ### The account is signed in but jobs still wait. Why? Check whether the account is paused, busy, out of usage limit, or reporting a proxy error. Signing in does not remove Muse's limits. --- # Create an image Create an image from a clear description in Studio, follow its progress, and find the finished file on your PC. Source: https://muse4ai.andrewbabo.com/docs/create-image · Updated 2026-11-02 ## Before you start - Have a Muse account ready with usage limit remaining. - Check that your library folder has room for new files. ## 1. Select Image Open Studio, choose Image, and use the text creation mode for a new image. For editing an existing picture, see [Reference files](https://muse4ai.andrewbabo.com/docs/reference-files). ## 2. Describe the result Describe the subject, setting, light, and style. For a shop photo, explain where the product should sit and what should be in the background. ## 3. Send once Choose an account or leave account selection automatic, then send the request. If no account is ready, the job waits in Queue. Do not send it again just because it is waiting. ## 4. Review the saved image Open the finished result in Studio or Library. Images normally arrive as WEBP, around 1920×1280; inspect the actual file before using it. ## Check it worked The job finishes, its image opens, and the downloaded file appears in Library. ## If it doesn't work ### Why is the job waiting? Check Accounts for a ready account with remaining usage limit and a working proxy. Also check whether other jobs are using the available parallel slots. ### The result is not what I wanted. What should I change? Make the description more specific or attach a reference image. Sending another request creates another job and uses your Muse usage limit. --- # Create a video Describe a short video in Studio, submit it to Muse, and review the finished clip before using it in your project. Source: https://muse4ai.andrewbabo.com/docs/create-video · Updated 2026-11-03 ## Before you start - Have a ready Muse account with usage limit remaining. - Plan one short scene and make room for the downloaded video. ## 1. Select Video Open Studio and select Video. Use the text creation mode to start from a description rather than an existing image or MP4. ## 2. Describe one short scene Muse clips are about 8–10 seconds. Describe the subject, its motion, the camera movement, and the setting rather than asking for many scenes. ## 3. Send and follow progress Choose an account or automatic selection, then send once. Follow the job in Studio or Queue. If it needs review, inspect it instead of submitting a duplicate. ## 4. Play the finished clip Open the result and check motion, framing, and sound. Typical output is 1280×720 with H.264 + AAC. Find the saved file in Library. ## Check it worked The finished clip plays in the app and its downloaded file is available in Library. ## If it doesn't work ### Why is the clip shorter than the story I described? Muse normally produces clips of about 8–10 seconds. Simplify the request to one scene; do not assume a longer prompt produces a longer video. ### An image-to-video or editing option is unavailable. Why? Some actions depend on what the current Muse version supports. Follow the app's notice rather than repeatedly resending the request. --- # Edit a video Attach an MP4 in Studio, describe the change in words, and Muse returns a new edited video while your original file stays as it was. Source: https://muse4ai.andrewbabo.com/docs/edit-video · Updated 2026-11-03 ## Before you start - Have a ready Muse account with usage limit remaining. - Keep the MP4 you want to change on your PC (a short clip works best). ## 1. Choose Video, then Edit video Open Studio and select Video. Open the creation method menu next to it and choose Edit video (MP4 → video). ## 2. Attach the MP4 Drag the MP4 into Studio or use the attach button. Check the small preview: it is the clip Muse will change. A video from Library can be attached the same way. ## 3. Say what should change Write one clear change, for example “make the light warmer and add a slow push-in at the end”. Name what must stay the same, such as the product or the person. ## 4. Send once and compare Send, follow the job in Studio or Queue, then play the new clip next to the original. The edited video is a new file in Library; the original is never overwritten. ## Check it worked A new edited clip plays in the app, appears in Library, and your original MP4 is unchanged. ## If it doesn't work ### The app refuses my file. Why? Edit video takes MP4 files only. Convert other formats to MP4 first, and keep the clip short; a very large file can take longer to send. ### Is editing the same as extending? No. Editing changes a clip you attach and returns a new clip. Extending continues a Muse video from Library and returns one longer video; see Extend a video. ### The result changed more than I asked. Ask for one change at a time and say what must stay the same. Muse decides the final look, so compare before you use the new clip. --- # Ask and research Ask Muse a question or attach research files in Studio, then read the answer and continue the same conversation. Source: https://muse4ai.andrewbabo.com/docs/ask-and-research · Updated 2026-11-02 ## Before you start - Have a ready Muse account and check that Ask is available. - Prepare a clear question and any files you have permission to share with Muse. - Consider a separate account for research because jobs on one account share its Muse memory. ## 1. Choose Ask Open Studio in Muse4AI and select Ask. Choose the account you want to use for this conversation. ## 2. Give context and attach files Explain the task and the format you need. For example, ask for a short summary of a sales report. Attach relevant files and check their names before sending. ## 3. Send and read the answer Send once and wait for the answer, which opens as an article. Check important claims against your source material before using them. ## 4. Continue or start fresh Use the conversation continuation option for a follow-up. A conversation stays on the account that created it. Choose a new conversation when you want a separate thread. ## Check it worked You can read the answer and either continue its conversation or start a separate question. ## If it doesn't work ### Why can I not switch accounts for a follow-up? The conversation belongs to its original Muse account. Start a new conversation to use another account. ### A file was refused. What should I check? Read the attachment warning and check the file type, size, and total attachments. A refused file is not included just because it was dropped into Studio. --- # Use reference files Attach reference images, video, or research files in the right Studio mode and check them before submitting a job. Source: https://muse4ai.andrewbabo.com/docs/reference-files · Updated 2026-11-02 ## Before you start - Have local files you have permission to send to Muse. - Have a ready account and decide whether you want image editing, video work, or questions about files. ## 1. Choose the right mode In Muse4AI Studio, use Image for image editing, Video for video requests, or Ask for questions about documents. Select an editing mode when working from an existing image or MP4. ## 2. Attach the files Use the attachment control to choose reference images. For video editing, use the MP4 attachment action in the appropriate mode. In Ask, attach documents through its file control or drop them into Studio. ## 3. Check the attachment list Check every thumbnail or filename and remove anything unrelated. Follow any size, count, or support warning. Do not assume all files from a multi-file drop were attached. ## 4. Explain how to use them Describe what should stay, what should change, or which question the files should answer. Send once, then review the result before making another request. ## Check it worked The intended files are visible in the composer before sending, and the result reflects the requested edit or question. ## If it doesn't work ### I dropped several images but not all appeared. Why? Media-mode drops can select only the first matching image. Use the attachment control to add more and check the visible list before sending. ### My MP4 was not attached when I dropped it. What now? Choose the video-editing mode and use its MP4 attachment action. General media drops are not a substitute for that control. ### Can I reuse a finished image? Yes. Open the image in Library and use its reference-image action to bring it back into Studio. --- # Follow jobs in Queue Track waiting and running jobs, preview finished results, and handle requests that need review without creating duplicates. Source: https://muse4ai.andrewbabo.com/docs/queue · Updated 2026-11-02 ## Before you start - Send a request from Studio, a batch, or a connected agent. - Keep Muse4AI running while it processes work. ## 1. Find the job Open Queue and identify the job by its thumbnail and prompt. Read its status before taking action: it may be waiting, running, finished, failed, cancelled, or awaiting review. ## 2. Preview a result Hover over or focus a job to open its quick preview. Use this to recognize the result without opening each job's full details. ## 3. Open full details Click the job to open its drawer. Check the prompt, result, files, and available actions. Open the finished file or its folder from here when those actions are available. ## 4. Handle review without resending Do not resubmit a job marked as needing review. The app is unsure whether Muse received it. Inspect Muse history and use Import from Muse history if a matching result exists; this retrieves a result rather than creating another one. ## Check it worked You can identify the job's current state, open its result, and avoid duplicate submissions when delivery is uncertain. ## If it doesn't work ### Why does a job stay in the waiting state? Check account readiness, usage limit, proxy health, and parallel-job availability. A paused batch can also keep its unsent jobs waiting. ### Is a job needing review the same as a failed job? No. Muse may already have received it. Do not use a fresh Studio request or another job to repeat it; inspect the original job and Muse history first. ### Why are retry actions different between jobs? Available actions depend on the job's state and whether the app knows Muse received it. Resolve the displayed cause instead of assuming every job is safe to resend. --- # Create and follow batches Turn a pasted or imported prompt list into a batch, check each row, and follow progress without sending jobs one by one. Source: https://muse4ai.andrewbabo.com/docs/batches · Updated 2026-11-02 ## Before you start - Prepare one prompt per line, or a TXT or CSV file. - Have ready Muse accounts with enough usage limit for the work you intend to send. - Review the list for accidental duplicates before importing it. ## 1. Create a batch In Muse4AI, open Batches and choose New batch. Give it a recognizable name and choose the default type, creation mode, repeat setting, and account. ## 2. Paste or import prompts Paste one prompt per line, choose a TXT or CSV file, or drop the file into the import area. Use the CSV sample shown in the app if you need columns for per-row settings. ## 3. Validate every row Run the list check, review the parsed rows, and fix errors. Check the total number of jobs, including repeats. Changing defaults applies to the next list check, so check again after changing them. ## 4. Start or save a draft Save a draft if the list is not ready. Otherwise, use the start button after confirming its job count. Each created job uses the selected accounts' Muse usage limit. ## 5. Follow the batch Open the batch to follow finished, running, waiting, failed, and review counts. Pause or resume when needed. Finished files appear in Library, grouped by the batch name. ## Check it worked The batch shows the intended number of jobs and its progress updates as results arrive in Library. ## If it doesn't work ### The imported text has strange characters. What should I do? The file may not be UTF-8. Open it in Notepad, save it with UTF-8 encoding, then import and validate it again. ### Why are there more jobs than prompt lines? Check the repeat default and any CSV repeat values. Repeated rows create separate jobs, so confirm the total before starting. ### Will cancelling the remainder stop jobs already generating? No. The confirmation states that waiting jobs are cancelled while generating jobs continue until finished. Do not resubmit jobs needing review. --- # Find and reuse results Find finished results in Library, filter by prompt or batch, open local files, and reuse an image as a Studio reference. Source: https://muse4ai.andrewbabo.com/docs/library · Updated 2026-11-03 ## Before you start - Finish a job and allow its result to download. - Keep the downloaded files available in their saved locations. ## 1. Open Library Open Library in Muse4AI. Browse the finished results, or narrow the view by type, batch, account, or favorites. ## 2. Search by prompt Use the prompt search to find words from the original request. If nothing appears, clear other filters and try a shorter phrase. ## 3. Preview and open the file Open an item to inspect it and its details. Use Open file to launch the saved file or the folder action to locate it on your PC. ## 4. Reuse an image in Studio For an image, choose Use as reference image. Check the attachment in Studio, describe the changes you want, and send only when ready. Reuse creates a new request; it does not change the original file. ## Check it worked You can find a finished result, open its local file, and bring a saved image into Studio as a reference. ## If it doesn't work ### Why is Library empty? Check that a job finished and its result downloaded. Clear search and filters, then inspect the job in Queue if the file is still missing. ### The app says the file is missing. What should I check? The file may have been moved or deleted. Restore it to its saved location if possible, then use Rescan to refresh the library's file status. ### Will changing the library folder move existing results? No. General settings changes the destination for new files only. Existing files remain in their original locations. --- # Extend a video Continue a Muse video from Library about 10 seconds per step, up to 6 steps (about 60 seconds), and get one longer video each time. Source: https://muse4ai.andrewbabo.com/docs/extend-video · Updated 2026-11-03 ## Before you start - Pick a video Muse made through Muse4AI: from Studio, a batch or an AI agent. - The Muse account that made the video must still be in Accounts, ready, with usage limit remaining. ## 1. Open the video and choose Extend video Open Library, click the video, and choose Extend video. If the button is grey, the line under it says why, for example that the account is missing or the video has no Muse conversation. ## 2. Choose how to continue Auto lets Muse continue the same scene. Based on description lets you write what should happen next, for example “the boat drifts under a small wooden bridge”. ## 3. Set how long Steps sets how many times to extend (1–6); Target length stops near the length you pick (up to 60 seconds). Each step is one Muse request and may use usage limit. ## 4. Start and follow the chain Choose Start extending. Each finished step adds one new, longer video to Library; the original stays as it was. Use View chain to see every step or to stop the chain. ## Check it worked Library shows a new video longer than the original, and the chain lists each finished step. ## If it doesn't work ### Why is Extend video greyed out? Read the line under the button. Common reasons: the account that made the video was removed, the video was made before this version saved its Muse conversation, or a newer video now continues that conversation. Make a new video, or extend the newest one. ### Does the account's run method matter? Yes. A video keeps the way it was made: one made over HTTP continues over HTTP, one made through the Muse page continues through the page. Keep the account on Auto and both work; the app tells you if the current setting blocks it. ### The join between steps is not smooth. Muse decides each continuation, so a seamless join is not guaranteed. Try Auto for the same scene, or describe the next moment more precisely. --- # Accounts and usage limits Check each Muse account’s usage, paused state, and parallel jobs before sending more work from the app or an agent. Source: https://muse4ai.andrewbabo.com/docs/accounts-and-limits · Updated 2026-11-02 ## Before you start - Add and sign in to your own Muse account first. - Muse4AI is free. Creating images and videos uses your Muse account’s usage limit. - Jobs on one account share that account’s Muse memory. Use a separate account for research you want to keep apart. ## 1. Check account readiness Open Accounts. Read each account’s state before assigning work. A paused account needs attention; adding parallel jobs will not fix it. ## 2. Read the usage panel Inspect the weekly limit and extra part reported by Muse. If Muse reports nothing left, automatic assignment skips that account. ## 3. Set parallel work carefully Open the account’s settings and choose its maximum parallel jobs. This controls simultaneous work, not the usage limit granted by Muse. ## 4. Resolve pauses before continuing For verification or expired sign-in, open the account window and complete the requested action yourself. For a limit or unsupported region, respect Muse’s restriction; do not change proxies to get around it. ## Check it worked You know which accounts can take work and which must wait or need your attention. ## If it doesn't work ### Why is an account skipped? Check its state and usage panel. An exhausted or paused account is not ready for automatic assignment. ### Does more parallel work give more usage? No. It only changes how much work can run at once. Muse still controls the account’s usage limit. ### Why do research answers share context? Jobs on one account share its Muse memory and history. Use a separate account and manage Muse memory yourself when separation matters. --- # Proxies and connection modes Choose a proxy and connection mode for each account, and understand when Auto pauses instead of switching paths. Source: https://muse4ai.andrewbabo.com/docs/proxies-and-modes · Updated 2026-11-04 ## Before you start - Have a working proxy you are allowed to use. - Each account uses its assigned proxy. There is no direct-connection fallback. - These settings control how Muse4AI reaches Muse, not how an agent reaches the app. ## 1. Test your proxies Open Settings › Proxy and use Test all. Fix a failing proxy before assigning it to an account. ## 2. Assign the account’s proxy In Accounts, use the account card’s menu to change its proxy. Each proxy shows which accounts already use it; sharing is allowed, but those accounts go out through the same IP address. A failed proxy does not cause the account to connect directly. ## 3. Choose a connection mode Open the execution method button on the account card. Auto (recommended) prefers HTTP and switches to page control only for technical errors. HTTP only uses the lighter channel; UI only controls the account’s Muse page and uses more memory. Changing the method applies to newly sent jobs. ## 4. Respect account pauses Verification, usage limits, and unsupported regions pause the account. Auto does not switch paths to get around these restrictions. ## Check it worked The account has a tested proxy and an appropriate connection mode, with no direct fallback. ## If it doesn't work ### Why does Proxy error stop the account? The app keeps the account on its assigned proxy. Test or replace that proxy instead of expecting a direct fallback. ### Will UI only fix a usage limit? No. A connection mode does not change the limits or region rules of your Muse account. --- # Connect your AI agent Connect an agent on this PC, a cloud agent, or an advanced command bridge with the right address and a separate key. Source: https://muse4ai.andrewbabo.com/docs/connect-overview · Updated 2026-11-02 ## Before you start - Keep the app open on your Windows PC and sign in to Muse. - Find out whether the agent runs on this PC or in the cloud. ## 1. Enable access and create a key Open Settings › API & agent. Enable API for agents and create a key named for this agent. Copy the key before closing its dialog. ## 2. For an agent on this PC Add an HTTP MCP server using http://127.0.0.1:47821/mcp and your key. Use the app’s current address if you changed its port. See [Claude Code](https://muse4ai.andrewbabo.com/agents/claude-code), [Cursor](https://muse4ai.andrewbabo.com/agents/cursor), or [Codex](https://muse4ai.andrewbabo.com/agents/codex). ```text MCP URL: http://127.0.0.1:47821/mcp Authorization: Bearer msk_YOUR_KEY ``` ## 3. For a cloud agent A cloud agent cannot reach this PC’s local address. Set up [Remote access](https://muse4ai.andrewbabo.com/docs/remote-access), then use the public MCP address and a key. See [Claude](https://muse4ai.andrewbabo.com/agents/claude) or [Lovable](https://muse4ai.andrewbabo.com/agents/lovable). ## 4. For local-command-only apps An advanced bridge runs a local command and forwards requests to the HTTP MCP server. Use the configuration in the agent’s guide rather than guessing a command. Browse [all agent guides](https://muse4ai.andrewbabo.com/agents). ## 5. No key at all: sign in with OAuth Apps such as ChatGPT, Claude, Codex or Cursor can connect with only the MCP address. See [Connect without a key (OAuth)](https://muse4ai.andrewbabo.com/docs/oauth). ## 6. Test before creating media Ask the agent to call muse_status first. Confirm it can see the app’s status before asking it to create an image or video. ## Check it worked The agent can read the app’s status using its own key and the correct local or public address. ## If it doesn't work ### Why does the local URL fail in a cloud app? A local address points to the computer making the request. Give a cloud agent the public address from Remote access instead. ### Why does the agent say unauthorized? Check that the key is active and sent as a Bearer authorization header. A public address does not replace the key. --- # Create and replace API keys Create one key per agent, copy it while it is visible, and replace or revoke it safely if access needs to change. Source: https://muse4ai.andrewbabo.com/docs/api-keys · Updated 2026-11-02 ## Before you start - Choose a clear name for the agent that will use the key. - Treat a key like a password. Do not put it in screenshots, public messages, or URLs. ## 1. Create a named key Open Settings › API & agent and create a key. Name it after the agent. Choose Create and cancel for generation, or Status only for monitoring. ## 2. Copy it once Copy the full key before closing the dialog; you cannot reveal it again. Paste it only into the intended agent’s protected configuration. ```http Authorization: Bearer msk_YOUR_KEY ``` ## 3. Replace and revoke safely To rotate a key, create a replacement, update the agent, test access, then revoke the old key. If a key was exposed, revoke it immediately. Revoking a key stops future authenticated access with it. ## Check it worked Each agent has a separately named key with the access it needs, and obsolete keys are revoked. ## If it doesn't work ### I closed the dialog without copying. Revoke that key and create another. The app does not reveal the original key again. ### Status works but generation fails. Check the key’s scope. A Status only key cannot create or cancel jobs. --- # Teach your agent with the Muse4AI skill Give your agent the Muse4AI skill or a short instruction note so it sends requests the safe way, without duplicates. Source: https://muse4ai.andrewbabo.com/docs/agent-skill · Updated 2026-11-02 ## Before you start - A skill is a small folder of instructions. It teaches the agent how to use Muse4AI; it is not the connection itself. - Connect the agent first with [Connect your AI agent](https://muse4ai.andrewbabo.com/docs/connect-overview). The skill never contains your key. ## 1. Open the agent panel In Muse4AI, open Guide and find the panel **For your AI agent**. It has three buttons: Copy instructions, Download skill, and Install for Claude Code. ## 2. Claude Code: install in one click Choose **Install for Claude Code**. The app shows the exact folder below and asks before writing. If the folder already exists, choose Replace or Cancel; Cancel changes nothing. Start a new Claude Code session afterwards. ```text %USERPROFILE%\.claude\skills\muse4ai ``` ## 3. Other agents with skills Choose **Download skill** to save a ZIP, or get the same file from the website: [muse4ai-skill.zip](https://muse4ai.andrewbabo.com/downloads/muse4ai-skill.zip). Unzip it into the skills folder your agent's documentation names, keeping the `muse4ai` folder intact. ## 4. Agents without skills Choose **Copy instructions** and paste the note into the agent's project instructions, such as AGENTS.md for Codex. The note has your PC's MCP address and the safe-use rules, but no key. ## 5. Check what the agent learned Ask the agent: "How should you create an image with Muse4AI?" A good answer mentions checking status first, a unique request ID, and waiting for the job instead of sending again. ## Check it worked Your agent follows the Muse4AI rules: it checks status, sends each request once, and waits for the result. ## If it doesn't work ### I installed the skill but the agent cannot reach Muse4AI. A skill teaches behavior only. The agent still needs the MCP address and an active key from [Create and replace API keys](https://muse4ai.andrewbabo.com/docs/api-keys). ### Claude Code does not use the skill. Start a new session so it reloads skills, and check that the folder contains SKILL.md directly inside `muse4ai`. --- # MCP tool reference Learn the MCP tools, follow a job through its states, and avoid duplicate submissions when a request is interrupted. Source: https://muse4ai.andrewbabo.com/docs/mcp-tools · Updated 2026-11-02 ## Before you start - Connect an MCP client with an active API key. - Generation uses your Muse account’s usage limit. Do not loop requests to overcome a limit. ## 1. Check the server and capabilities Open Settings › API & agent, then call muse_status to read account readiness, usage, and available capabilities. ## 2. Choose the right tool Tool — purpose: - `muse_status` — read status and capabilities. - `muse_generate` — queue image or video work. - `muse_chat` — ask Muse; receive its answer unchanged, files, and a conversation_id. - `muse_get_job` — read or wait for one job. - `muse_list_jobs` — list jobs created with this key. - `muse_cancel_job` — request cancellation of your job. - `muse_extend_video` — start a supported video-extension chain. - `muse_get_extend` — inspect or wait for an extension chain. ## 3. Submit once, then poll Call muse_generate with a unique request_id for each new operation. Then call muse_get_job with wait_seconds until succeeded, failed, cancelled, or needs_review. On success, use download_url. Reuse the same request_id and unchanged input only when retrying the same interrupted submission. ```json { "kind": "image", "prompt": "A ceramic cup on a wooden desk", "request_id": "muse4ai-image-example-001" } ``` ## 4. Apply the retry rules Never resubmit running or needs_review work. Failed jobs may be retried only for PRE_SUBMIT_TRANSIENT or PROXY_FAILED, or once after a few minutes for PROVIDER_ERROR. A person must inspect needs_review work in the app. ## 5. Handle conversations and extensions Keep conversation_id to continue a chat. A conversation_busy result means wait, not resubmit in a loop. Use muse_extend_video only when muse_status reports the extension capability, then follow it with muse_get_extend. Extra length and seamless continuity are not guaranteed. ## Check it worked Your client tracks existing jobs, preserves request IDs, and stops for human review when required. ## If it doesn't work ### The request timed out. Should I create another? Check the existing job first. If retrying an interrupted submission, keep the same request_id and input to avoid duplicates. ### Why can I not see another agent’s jobs? The listing tool returns jobs created with the current API key. ### Does chat verify Muse’s answer? No. The answer is returned unchanged. Check research claims and attached files yourself. --- # REST API reference Use the local REST API with a Bearer key, inspect its OpenAPI document, and follow jobs without submitting duplicates. Source: https://muse4ai.andrewbabo.com/docs/rest-api · Updated 2026-11-02 ## Before you start - Enable API for agents and create a key with the required scope. - The default base URL is http://127.0.0.1:47821/v1. Use the app’s current address if its port changed. ## 1. Check server access Open Settings › API & agent. Keep access local unless another machine needs it. Send your key in Authorization: Bearer, never in the URL. ## 2. Read status Run this in a terminal, replacing the placeholder with your own key. On Windows, curl.exe avoids a PowerShell command alias. ```powershell curl.exe "http://127.0.0.1:47821/v1/status" -H "Authorization: Bearer msk_YOUR_KEY" ``` ## 3. Choose an endpoint Paths below are relative to the base URL: - GET /health — liveness; no key required. - GET /openapi.json — API schema; no key required. - GET /status — readiness and capabilities. - GET or POST /jobs — list or submit jobs. - GET /jobs/{id} — job details and results. - POST /jobs/{id}/cancel — request cancellation. - POST /references — upload reference bytes. - GET or HEAD /assets/{id}/content — fetch an output with a key or valid signature. - GET /conversations/{id} — read a conversation. - POST /assets/{id}/extend or /conversations/{id}/extend — start an extension. - GET /extend-chains/{id} — read an extension chain. - POST /extend-chains/{id}/cancel — cancel a chain. ## 4. Use the live schema The server exposes its OpenAPI document at http://127.0.0.1:47821/v1/openapi.json without a key. Read it for request fields and responses. Give each new submission a unique request_id; preserve it when retrying the same interrupted request. ## 5. Follow the existing job Poll the returned job ID. Never resubmit running or needs_review work. Follow the [MCP retry rules](https://muse4ai.andrewbabo.com/docs/mcp-tools), which apply to the same underlying jobs. ## Check it worked An authenticated status request succeeds and your client can read the server’s schema. ## If it doesn't work ### Why does health work but status fails? Health is public. Status requires an active key in the Bearer header. ### Why do I get not found? Check that the base includes /v1, and compare the route and method with the OpenAPI document. --- # Connect without a key (OAuth) Paste only the MCP address into ChatGPT, Claude, Codex or Cursor, then approve with the 6-digit code shown in Muse4AI. Source: https://muse4ai.andrewbabo.com/docs/oauth · Updated 2026-11-03 ## Before you start - Keep the app open and turn on API for agents in Settings › API & agent. - For cloud apps such as ChatGPT or the Claude app, turn on Remote access first so you have a public address. ## 1. Copy the MCP address In Settings › API & agent, open the “No key (OAuth)” template and copy the address ending in /mcp. Cloud apps need the public address from [Remote access](https://muse4ai.andrewbabo.com/docs/remote-access). ```text https://your-address.example/mcp ``` ## 2. Add it in your AI app Add a new MCP server or connector and paste the address. When asked how to sign in, choose OAuth. Do not add any key. ## 3. Approve with the 6-digit code A Muse4AI approval page opens showing the app’s name and what it asks for. Type the 6-digit code shown in the Muse4AI window and press Allow. There is no account or password: whoever sits at this PC decides. ## 4. Disconnect any time Connected apps are listed in Settings › API & agent › Connected apps. Disconnect one and its next request is refused. ## Check it worked The AI app shows Muse4AI as connected and can call muse_status without any API key. ## If it doesn't work ### The app keeps asking for a key. Choose OAuth (not API key or header) as the sign-in type, and make sure the address ends in /mcp. ### It worked yesterday and stopped today. A Quick tunnel address changes every time the app starts. Use a named tunnel or your own domain for a stable address, then reconnect. --- # Remote access Let a cloud agent reach your PC through a tunnel or HTTPS domain, or share only within a trusted private network. Source: https://muse4ai.andrewbabo.com/docs/remote-access · Updated 2026-11-02 ## Before you start - Enable API for agents and create a separate key for the remote agent. - Keep this PC awake and the app running while remote agents need it. - A public address makes the server reachable; it does not remove key requirements. ## 1. Choose who can connect Open Settings › API & agent. The access choices are This machine only, Private network, Quick tunnel, and Named tunnel. ## 2. Use a Quick tunnel for a temporary link Confirm public sharing and wait for the tunnel to be online. The app uses cloudflared. The address changes each time the app starts, so update your cloud agent after a restart. ## 3. Choose a fixed address if needed A named tunnel uses your Cloudflare setup and domain. The separate domain section can provide direct HTTPS using App-managed HTTPS with Caddy, or an Existing HTTPS proxy such as Caddy, nginx, or IIS. Follow its DNS and connectivity checks; these routes can coexist with a tunnel. ## 4. Use private sharing only where reachable Private network is for devices that can reach your PC through a LAN or private network such as Tailscale. It is not automatically a public link for a cloud service. ## 5. Copy the address and limit exposure Use the current public base with /mcp for MCP or /v1 for REST, plus the agent’s key. Turn off sharing when it is not needed; disable a separately enabled domain too. ```text https://your-tunnel.trycloudflare.com/mcp Authorization: Bearer msk_YOUR_KEY ``` ## Check it worked The intended remote agent can read status with its key, and unnecessary sharing is off. ## If it doesn't work ### Why did yesterday’s link stop working? Quick tunnel addresses change at app startup. Copy the current address into the agent again. ### Why does a public URL still need a key? The tunnel changes reachability, not authorization. Protected operations still require an active key. ### Does turning off the tunnel stop my domain? The domain is configured separately and can run alongside a tunnel. Check both, or disable the API entirely. --- # Find the right setting Find language, output folders, job controls, notifications, agent access, security, and diagnostics in Settings. Source: https://muse4ai.andrewbabo.com/docs/settings-overview · Updated 2026-11-02 ## Before you start - Decide what you want to change before changing several settings at once. - Keep Muse4AI open so you can check the result of each change. ## 1. Start with General Open Settings › General for language and the Library folder. English is the default; Vietnamese is also available. ## 2. Find work and connection controls Use Proxy for proxy management, Job execution for the direct channel and app-wide limits, Queue for retries, and Notifications for alerts. Each account’s execution method is on its card in Accounts. ## 3. Manage agent access API & agent contains the server switch, port, keys, agent configuration, and remote sharing. Leave remote sharing off unless another machine needs access. ## 4. Find support information Check Security for security settings, Diagnostics for an exportable diagnostics ZIP, and About for the installed version, maker, and acknowledgments. ## Check it worked You can find the setting you need without changing unrelated controls. ## If it doesn't work ### Where is the account’s connection mode? Open that account’s settings in Accounts, not the API server settings. ### Where can I check the installed version? Open Settings › About before reporting a problem. --- # Updates, rollback, uninstall, and backups Update from inside the app without losing data, go back to the kept previous version, uninstall cleanly from Windows Settings, and recover from a backup. Source: https://muse4ai.andrewbabo.com/docs/updates-and-backups · Updated 2026-11-06 ## Before you start - Finish or inspect active jobs before quitting. Do not delete the data folder to update. - The app installs in %LOCALAPPDATA%\Programs\Muse4AI; its roaming data is in %APPDATA%\MuseStudio. Output files live separately. ## 1. See your version and the update check Settings › About shows the version you use and an Updates card. When the app opens and every 12 hours it reads one small file on the Muse4AI website to see whether a newer version exists; it sends none of your data. Turn the switch off to stop checking, or press Check now at any time. ## 2. Update from inside the app When a newer version is out, a dot appears next to Settings and the app tells you once. Open Settings › About and choose Download and install: the app downloads the installer, checks its SHA-256 fingerprint, then closes, installs, and opens again in about a minute. Sign-ins, settings, queue, and library are kept. If jobs are running it asks first: jobs already sent are reconciled when the app reopens, jobs not yet sent stay in the queue. ## 3. Or install the newer package yourself You can still run a new EXE installer from the website (it closes the app for you), or extract the new ZIP, quit from the tray icon, and run install.ps1. Installing over the current version keeps your data the same way. ## 4. Understand automatic backups Database backups are stored under %APPDATA%\MuseStudio\backups. The app keeps daily backups and makes a backup before a data-schema upgrade. These database copies are not a backup of your output files or every sign-in file. ## 5. Restore only when needed At startup the app checks the database. If it is corrupt, it offers the newest backup that passes its check and keeps the damaged files for diagnosis. Changes after the backup may be lost; library files remain separate. ## 6. Go back to the previous version Each update keeps one previous version on the PC. If the new one has a problem, open Settings › About › Previous version and choose Go back to this version; the app closes and opens the older one with the same data. It only offers this when that version can read your current data — after a data-store upgrade an older version cannot, and the card says so. Without the app, the uninstall window offers the same rollback, or run the command below. ```powershell powershell -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\Programs\Muse4AI\tools\install.ps1" -Rollback ``` ## 7. Uninstall from Windows Settings Open Windows Settings › Apps › Installed apps, find Muse4AI and choose Uninstall. A small window asks whether to also delete accounts, proxies, settings, and sign-ins saved on this PC; leave it unticked to keep them for a later reinstall. Images and videos in your library are always kept. If the app is open, it is asked to quit the normal way first. ## 8. Export diagnostics for support Open Settings › Diagnostics and export the diagnostics ZIP. Review what you share. If the app cannot start, preserve its logs and describe the startup error. ## Check it worked The intended version opens with your data, or you have a preserved backup and diagnostics for recovery. ## If it doesn't work ### The installer says the app is still running. The EXE waits about 45 seconds for the app to quit. If jobs are still running, Muse4AI first asks whether to quit. Answer it or let the jobs finish, quit from the tray icon (closing the window alone does not stop the app), then run the installer again. ### The Updates card says this copy cannot install by itself. That copy was not installed with the EXE or install.ps1 (for example it runs from another folder). Open the download page, run the installer once, and later updates work from inside the app. ### Checking for updates failed. Usually the PC is offline or the website could not be reached. Nothing else is affected and the app keeps working; it tries again in 12 hours, or press Check now. A download that does not match its SHA-256 fingerprint is deleted and never run. ### Will restoring a backup keep recent changes? Not necessarily. Jobs and settings changed after that backup can be lost. Keep the current files before manual recovery. ### Are my videos inside the database backup? No. Back up the output folder separately if you need an independent copy of your media. --- # Privacy and your data See what stays on your PC, what your prompts and attached files send to Muse, and how to limit agent access safely. Source: https://muse4ai.andrewbabo.com/docs/privacy-and-data · Updated 2026-11-06 ## Before you start - Only attach files you are allowed to send to Muse. - Review your agent provider’s data practices separately; its service is outside the app. ## 1. Know what stays on this PC Muse4AI keeps jobs, settings, API-key records, downloaded files, and account sign-in sessions in its own local storage. It does not store your Muse password. Roaming data is under %APPDATA%\MuseStudio; media uses your chosen output folder. ## 2. Know what is sent to Muse Your prompts and attached files are sent to Muse through your own account so it can answer or generate results. Jobs on one account share its Muse memory and history. Avoid sending confidential material without permission. ## 3. Understand the project boundary The app does not send your jobs, files, keys, or sign-in sessions to Andrew Babo or the Muse4AI website. Its update check only downloads a small public file from the website (you can turn it off in Settings › About). Connecting an agent or enabling a tunnel introduces the separate providers you choose. ## 4. Limit access and shared material Use one key per agent, keep sharing off when unnecessary, and revoke unused keys. Review diagnostics and screenshots before sending them. Never include a full API key in a screenshot or URL. ## Check it worked You know which data stays local, which goes to Muse, and who can access the app through your keys. ## If it doesn't work ### Does no password storage mean no session storage? No. The app retains sign-in sessions in its own storage so accounts can stay signed in. ### Can I isolate research between agents? Separate API keys control access, but jobs on one Muse account still share that account’s memory. Use separate accounts when separation matters. --- # Troubleshooting Resolve common sign-in, queue, connection, and installation problems without accidentally sending the same job twice. Source: https://muse4ai.andrewbabo.com/docs/troubleshooting · Updated 2026-11-02 ## Before you start - Keep the error message and note which account, job, or agent is affected. - Do not resubmit running or needs_review jobs while investigating. ## 1. Inspect the existing job Open Queue and select the job. Read its state and error before retrying. For needs_review, inspect Muse history rather than immediately creating another job. ## 2. Check the affected connection For account problems, check Accounts and the assigned proxy. For agent problems, check Settings › API & agent, the current address, and the key. ## 3. Collect a useful report Record the app version, what you tried, and the exact error. Export a diagnostics ZIP from Settings › Diagnostics. Remove exposed keys from anything you share. ## Check it worked You have resolved the issue or collected a clear report without duplicating work. ## If it doesn't work ### The account needs verification or sign-in. Open the account window using Take over, complete the requested action yourself, then check the session again. Do not automate around verification. ### The account is paused for a usage limit. Check the usage panel and wait for availability reported by Muse. Increasing parallel work does not restore usage. ### Muse reports an unsupported region. Stop using the affected account for this work and respect Muse’s restriction. Do not use proxies or connection modes to bypass it. ### My Quick tunnel link stopped working. Its address changes each time the app starts. Copy the current public MCP address into the agent and retain its key. ### The agent says unauthorized. Use an active key in Authorization: Bearer. msk_YOUR_KEY is only a placeholder. If the original key is lost, revoke it and create another. ### The API port is busy. Use the free port suggested in Settings › API & agent, then copy the updated address into every affected agent. ### Windows SmartScreen warns about the installer. The app is not code-signed. Only if you trust the downloaded package, choose More info → Run anyway. Do not disable Windows protection globally. ### A job needs review. The app is unsure whether Muse received it. Inspect the job and Muse history. Import an existing result when available; sending again can create a duplicate and use more of your limit. ### The video is shorter than requested. Muse clips are about 8–10 seconds. Prompting for more does not guarantee length. Extension is available only when reported by the server, and added duration is not guaranteed. ### The app disappeared after I clicked X. It is hidden in the system tray. Open it from the tray icon. To stop it fully, right-click that icon and choose Quit. ### The account reports a proxy error. Test proxies in Settings › Proxy and fix or replace the assigned proxy. The app does not fall back to a direct connection. ### Downloads paused because the disk is nearly full. Free space on the output drive or change the output folder in Settings › General. Downloads can resume when space is available. --- # Glossary Look up unfamiliar app and agent terms in plain language, then return to the guide you were reading with more context. Source: https://muse4ai.andrewbabo.com/docs/glossary · Updated 2026-11-02 ## Before you start - You do not need programming knowledge to use this glossary. - Keep the unfamiliar word or the guide you were reading in mind. ## 1. Start from your guide Open Guide in Muse4AI. In supported articles, the first use of a glossary term links to its explanation. ## 2. Read the list below The glossary list appears automatically below this article. Find the term and read its short explanation. ## 3. Return to the task Return to your guide and continue the next step. For connection terms, start with [Connect your AI agent](https://muse4ai.andrewbabo.com/docs/connect-overview). - **AI agent** — An AI assistant that can use tools for you — for example Claude Code, Codex or Cursor. Muse4AI is one of those tools. - **MCP** — Model Context Protocol: a common plug that lets an AI agent use outside tools. Muse4AI offers one at the address ending in /mcp. - **API** — A way for programs to talk to each other. Muse4AI's API lets scripts and agents send jobs and fetch results. - **API key** — A long password (it starts with msk_) that an agent sends with each request. You create, copy and delete keys in Settings › API & agent. - **Tunnel** — A safe public web address that leads to Muse4AI on your PC, so cloud apps like Claude or Lovable can reach it. Your API key is still required. - **Proxy** — A separate internet connection given to one Muse account so each account keeps its own connection. It is not a way around Muse's rules or limits. - **Usage limit** — How much your Muse account can still create. It belongs to your Muse account; Muse4AI only reads and shows it. - **Agent Skill** — A small folder of instructions (SKILL.md) that teaches an AI agent how to use a tool well. - **Queue** — The list of every job — waiting, running, done or failed — with a picture and the prompt. ## Check it worked You understand the term well enough to continue your task. ## If it doesn't work ### Do I need to memorize these terms? No. Look them up when needed and follow the practical steps in the guide. ### What if a term is not listed? Read the surrounding explanation in the relevant guide. For an agent-specific term, consult that agent’s documentation. --- # Open source and acknowledgments See the projects behind Muse4AI, starting with muse2api, and find acknowledgments and installed license texts. Source: https://muse4ai.andrewbabo.com/docs/open-source · Updated 2026-11-02 ## Before you start - This page explains project acknowledgments, not instructions for connecting an agent. - Muse4AI is an independent project by Andrew Babo, not affiliated with or endorsed by Meta. ## 1. Thank the muse2api projects first The Muse web integration builds on work from [muse2api by czg86389-hub](https://github.com/czg86389-hub/muse2api) and [muse2api by www222fff](https://github.com/www222fff/muse2api). Thank you to their authors for the foundations used in page interaction and result handling. ## 2. Read the complete acknowledgments The complete list of libraries, fonts, tools and app components, with what each one does and its license, is on the [Open source page](https://muse4ai.andrewbabo.com/open-source). In the app, the same list also appears right below this guide. ## 3. Find the installed license text Open Settings › About for the app’s acknowledgments. The muse2api license text is also shipped in the installation folder at the path below. ```text %LOCALAPPDATA%\Programs\Muse4AI\resources\muse2api.txt ``` ## Check it worked You can identify the upstream projects and locate their acknowledgments and shipped license text. ## If it doesn't work ### Does an acknowledgment mean a partnership? No. Acknowledgments credit work used by the project; they do not imply an affiliation or endorsement. ### Where is the full dependency list? Read the automatically rendered credits below this article. Consult each entry’s linked project and license for details. ---