Cloud workspaces
Sign in to a workspace, discover permitted agents and track submitted cloud work.
In this topic
Mellow gives you two different ways to work beyond the Mac in front of you. A connected device runs work on a Mac you paired. A Cloud workspace gives your signed-in account access to the agents and resources that a workspace server publishes. Choose the destination according to where the work belongs.
A local project is a third concept: it organizes work and files on a host. Creating a project does not establish a cloud account or pair another computer.
Choose where the task belongs
| Destination | What authorizes access | Where the work runs | What to check first |
|---|---|---|---|
| This Mac | Your local Mellow session and agent permissions | This Mac | Model readiness and working folder |
| Paired Mac | Verified device connection and its access grant | The selected Mac | Host identity, reachability, and access expiry |
| Cloud workspace | Browser sign-in, workspace membership, and server permissions | The workspace's published execution environment | Correct account, workspace, and available agent |
Signing in to Cloud does not grant ownership of your Macs. Pairing a Mac does not grant a cloud role. Keep those connections separate when investigating an error.
Connect a Cloud workspace
- Open Mellow Cloud in Mellow's management window.
- Add the workspace server supplied by your administrator. Use its HTTPS origin; a supported
/mcpaddress is also accepted. Do not paste an authorization page containing query parameters. - Continue in the browser. Check the account and workspace shown before authorizing.
- Return to Mellow. Confirm that the authenticated workspace card shows the intended server, account, and workspace.
- Refresh the workspace and load its published agents.
Mellow verifies the authorization server and token endpoint against the selected service. A login that merely identifies you is insufficient: the grant must authorize the workspace API. If the browser reports a redirect mismatch or Mellow reports an issuer mismatch, the service's OAuth configuration needs correction; repeatedly approving the same broken request will not repair it.
Understand the connection status
Authentication, MCP discovery, the resource catalog, and agent discovery are separate checks. One can succeed while another fails.
- Authenticated workspace means Mellow verified account and workspace identity.
- Discovered tools is the count returned by that server's MCP tool catalog. Five tools is not a count of agents, models, or all the tools installed on your Mac.
- Workspace catalog describes resources available through the selected connection. A catalog conflict can occur while the account remains signed in.
- Published agents are the destinations available to the current account. An empty list can mean no agents are published or none are visible to your role.
A green connection badge is therefore a prerequisite for cloud work, not proof that a task has completed successfully.
Send a task and follow its result
Choose an available cloud agent, enter the task instructions, and add only the context it needs. The Cloud task form does not automatically attach your local files, current chat, or project. Review the context as the package being handed to another environment.
After submission, use the tracked task entry to inspect state and retrieve the result. Closing the settings page does not cancel a submitted task. Use the task's cancellation control when you intend to stop it; a cancellation request and a confirmed cancelled state are different outcomes.
For a first test, send a short instruction with a recognizable expected answer. Verify submission, terminal state, and returned text before attempting a task that depends on files or tools.
Switch, sign out, or remove
Use the saved connection list to choose a workspace. Add another connection when authorizing a different account or workspace; Mellow checks that a refreshed grant still matches the saved identity.
Sign out ends local use of the grant and attempts server revocation. Remove connection also removes the saved connection entry. If Keychain removal fails, the connection may be disabled while credentials still require cleanup. Read the error before assuming removal completed. Server-side token revocation may be unavailable; an explicit warning explains when existing tokens can remain valid until expiry.
Resolve common failures
| Symptom | Meaning and next step |
|---|---|
| HTTP 409 in the catalog | Inspect the named resource or tool schema on the server. Signing in again does not fix a catalog conflict. |
| No published agents | Check publication and account permissions in the same workspace used for sign-in. |
| Wrong workspace after consent | Add that workspace separately, or repeat sign-in with the intended selection. |
| Sign-in succeeded but MCP failed | Check the MCP endpoint and tool discovery diagnostics independently of account identity. |
| Paired Mac is missing | Open Devices; this is a device connection, not Cloud sign-in. |
| A local model works but Cloud does not | Local inference does not validate server configuration, membership, or published agents. |
Access and data boundaries
The workspace server determines membership and resource permissions. This guide does not imply a particular subscription, trial, credit pool, or billing plan. Use the account and service information actually presented by your deployment.
A cloud agent receives the task and context you submit under your workspace role. A paired Mac uses its host's execution and approval rules. Neither connection should be treated as permission to copy a whole local workspace implicitly.
Continue with Devices and Mobile, MCP services, or Access and identity.
Continue exploring · Connect your workspaceMessaging channels →Connect incoming conversations, configure replies and review outbound behavior.