Connected apps and permissions

Approve a connection when you want an app or assistant to perform the actions listed on its permission request. You can review or disconnect it later in Connected apps.

Read the permission request

Check the app's name and the requested actions before approving a connection. Reading guides, editing a project and running a credit-consuming generation job are different permissions.

Requested access	What to consider
Read guides or projects	An assistant may need your saved project and source to help with it
Create or change work	Approve this when you want the tool to make the stated changes in your account
Generate audio	This can use your shared account credits; review the generation request and budget
App identity or presets	These apply to the registered app and its supported preset context

An assistant uses the permissions you grant. Tell it which project to work on, what it should change and whether it may spend generation credits. Using Maru with an assistant introduces the available paths.

Review existing access

The page lists apps and AI agents you have approved. Check the app name, granted permissions, connection date and last recorded use. For Reconnect required, return to the app's sign-in flow if you want to reconnect. An app marked App disabled has no current access while it remains disabled.

An agent connection may identify the service it connected through or say it came from an app on your computer. Use that information to recognize the connection. Generation-enabled connections use the same account credit balance; Usage and credits is where to review consumption.

Creator apps manages registrations you own, rather than apps you have connected as a user. If you are building a product, read Add Maru sign-in to your product.

Disconnect an app or assistant

Find the connection, choose Disconnect and confirm. This removes that connection's Maru access across its devices. Your saved projects, presets, memberships and purchases stay in your account. Material the app already exported or copied is not removed by disconnecting it.

To stop using an agent integration, also remove Maru from the agent's connector settings. Otherwise it may ask you to approve another connection. Reconnecting requires a new permission decision.

Manage tokens and local sign-ins separately

Access tokens manages personal tokens and sign-ins used by the CLI and desktop tools. These are separate from the app and agent connections above. Review each token's name, permissions and last-use information, then use Revoke for access you no longer need.

If a script requires a personal token, choose New token, give it a recognizable name and select only the permissions it needs. Copy the new secret into your tool's secure configuration while it is displayed. Maru shows it once; if you lose it, create a replacement and revoke the unused token.

Connect Studio provides a fallback pairing code when an available desktop Studio installation cannot complete its normal browser sign-in. The code works once and expires. Use it only in Studio's sign-in screen; the page does not install the app or synchronize local folders.

Keep credentials private

Use the supported sign-in or consent flow. Do not paste tokens into public projects, shared screenshots or support messages. If you suspect unwanted access, follow account security.

For generation, read generation and credits before approving spending access.

Access, purchases and private data

Signing in identifies you within the connected app. It does not automatically give that app your private projects or purchase access, and it does not authorize generation spending without the relevant consent.

A plugin's activation is a separate product-access flow. See licenses and product access when a purchased release asks you to approve a computer.

Developers connecting local tools can continue with the CLI sign-in reference.