Account & device setup

Open Muster on the web, connect a model provider, and choose the tools your team can use. Muster is a free app. You supply your own provider API key and pay that provider for usage; connected services can have separate charges.

Managed web service Bring your own API key Device access by permission

1. Open your workspace

Go to Open Muster and sign in using an option shown there. Follow the setup steps for your account. You do not need to deploy a server or configure a hosting service.

A Muster account, a model-provider account, and permission to use a connected app are separate. Signing in to Muster does not supply a provider API key or authorize access to your files.

2. Connect your model provider

Use the provider step in setup or Settings → Providers to save a supported provider API key. Choose an available engine and model for your bot, then send a small first task. Provider availability, rate limits and charges come from the provider account you connect.

Muster's free app does not include paid model usage. Check your provider's billing and limits before starting recurring work. See Engines & models for supported connection types and existing desktop CLI options.

3. Choose where work runs

Start with the tools available in your workspace. For work that needs a device, install an available Muster desktop app and follow the connection and permission steps it offers. Review the selected computer and the action before granting access.

Local files, local models, screen control and device tools need an available, capable computer and its permissions. Opening the website does not give it access to another computer. A sleeping or disconnected device cannot carry out device tasks.

Existing installations Released desktop and companion versions can have their own workspace data and connection steps. Signing in with the same account does not by itself merge workspaces, route tasks to every device, or synchronize all history. Keep existing data until you have checked the destination workspace and any restore result.

4. Review connected apps and Drive consent

Connect only the services you want Muster to use, and read the permissions shown during authorization. App connections and individual task approvals are separate decisions.

If your current setup asks you to connect Google Drive, follow that step and review its consent screen. Signing in with Google is separate from granting Drive access. Use the backup and restore controls offered by your version; check what a backup contains before relying on it.

Existing desktop backup controls support manual export and restore, with Drive connection available in supported versions. Check the listed contents and restore requirements for your version. Drive connection alone does not establish automatic synchronization, complete recovery, or a backup of every provider credential. A successful sign-in is not evidence that a backup or restore has completed.

Where data and keys live

What you use	Where it is handled
Hosted workspace	The Muster service stores and processes workspace records. Model requests and tool activity can send relevant content to the services you connect.
Provider keys saved in the web app	The service stores account-scoped provider credentials in an encrypted vault and uses them for your requests. This is server-side custody, not a promise that keys stay only on your device.
Existing desktop installation	Its local workspace and configuration can remain on that installation. Provider and connected-app calls still use the network as needed.
Phone and Watch companions	Supported actions use a paired connection. The app may keep local session data, drafts or cached content; it is not a complete workspace backup.

See the privacy policy for data handling and Approvals & privacy for action controls. For your first conversation, continue with Quick start.