How Muse4AI works
Three parts, all of them yours: your AI agent, the Muse4AI app on your Windows PC, and your Muse account.
- 1
Your AI agent
Claude Code, Codex, Cursor or another agent decides what to make and sends a request with its own key, through MCP or REST.
- 2
Muse4AI on your PC
The app checks the key, puts the request in the Queue, picks a ready Muse account, sends it once and saves the result to your Library.
- 3
Your Muse account
Muse makes the image, video or answer under your account and its usage limit, through the proxy you set for that account.
Where your data lives
- Accounts, settings, the Queue and Library records stay in %APPDATA%\MuseStudio on your PC.
- Finished files go to the library folder you choose.
- You sign in to Muse yourself; the app keeps the session, not your password.
- API keys are stored only as a fingerprint (hash); the full key is shown once when you create it.
Rules that keep jobs safe
- Each request carries its own ID, so a retry after a dropped connection does not create a second job.
- If the app cannot tell whether Muse received a job, it marks it for review instead of sending it again.
- When Muse asks for verification, reports a limit or an unsupported region, the account pauses until you act.
- A broken proxy stops its account; the app never switches to a direct connection.