# A cloud for agents, with the work kept together. Reviewed: 2026-10-20 Canonical: https://clankercloud.ai/learn/agent-cloud Clanker Cloud brings persistent Projects, managed Sessions, saved files, reusable Agents, and selected hosted execution into one agent cloud workflow. Connect ChatGPT, Claude, Hermes, or OpenClaw through compatible MCP and browser OAuth, then use only the tools and access needed for the task. Hosting the assistant itself is a separate choice. ## What you are working toward A clear division between your assistant, its cloud tools, saved work, and the person who approves the result. ## Start with - A Clanker Cloud Workspace account - A compatible agent client or native Workspace Agent - One task with approved data, output checks, and an owner ## Use cloud resources around a concrete deliverable An agent cloud becomes useful when it helps finish work: a source-based brief, a checked spreadsheet, a private App, or a repeatable specialist. Start with one deliverable and keep its sources and review criteria in a Project. Add compute or a cloud browser when the task needs them rather than making every request a machine-management exercise. For example, a consultant can keep approved notes in a Project, ask ChatGPT to prepare a saved report, and ask Claude to review the conclusions. A technical operator can connect Hermes or OpenClaw to the same authorized Workspace tools. Each client still needs its own working connection; the Project does not synchronize private conversations between providers. ## Choose the assistant and connect its tools | Client | Start here | Check before real work | | --- | --- | --- | | ChatGPT | Use the ChatGPT Workspace connection guide | Enable the plugin, complete OAuth, and verify current tools | | Claude | Use the Claude Workspace connection guide | Enable the connector and check account or organization availability | | Hermes | Use the Hermes Workspace guide and official MCP setup | Confirm remote HTTP and OAuth support in your installed version | | OpenClaw | Use the OpenClaw Workspace guide and official MCP setup | Configure Streamable HTTP with OAuth and verify the connection | ## Grow from files to Apps and reusable Agents Use saved-work tools for Projects, files, task records, and handoffs. Discover native tools when the job needs Office files, Agent configuration, compute, a hosted browser, or App work. Tool discovery returns the current schemas and required permissions; a catalog entry does not prove that every account, provider, or client can run it. Create a custom Agent when the method should be reused. Define accepted inputs, selected tools, exception behavior, and a review checklist, then test it. Build a private App when people need an interactive tracker or dashboard. A draft, a ready preview, a published App, and a successful Agent run are distinct results; verify the one the user requested. ## Keep access and usage understandable The MCP connection uses browser OAuth. Read is the starting point; Edit permits saved-work changes, while Configure and run enables execution and configuration within the user’s role. Choosing a Project does not turn a broader account-role grant into a Project-only credential. Plan checkout is a separate permission, not a prerequisite for a connection test. Your external assistant’s model usage remains with its provider. Clanker-hosted inference, compute, builds, and other enabled operations follow their applicable usage rules. A client subscription does not make all Workspace work free. Inspect account usage and stop environments or recurring workers you no longer need. Sources: - [Clanker: connect an external agent and review permissions](https://clankercloud.ai/workspace-agents) - [Clanker: current usage and plans](https://clankercloud.ai/pricing) ## Choose the cloud interface that matches the job Use Workspace MCP when an external assistant should work with your Projects and authorized tools. Use a supported hosted Agent environment when you want to configure agent execution in Clanker. Use the standalone Sandbox API when your own application needs a programmatic runtime under that separate API contract. Use a connected computer only when the task needs that particular machine or local application. A connection to Workspace does not expose your local desktop automatically. Recurring Loops and Schedules also require their own configuration. Keep these choices explicit so saved context, active processes, permissions, and costs are not confused. ## Try this prompt Copy into a Workspace Session. Opening Workspace does not send it automatically. ```text Help me choose how to use Clanker Cloud for one agent workflow. Ask what should be saved, which assistant I use, whether code or browser execution is needed, and who reviews the result. Recommend Workspace MCP, a supported hosted Agent environment, or the separate Sandbox API based on those requirements. Begin with a read-only connection check if applicable. Do not start compute, change permissions, make a purchase, or configure recurring work until I authorize the specific step. ``` ## Common questions ### Can Clanker Cloud be used with ChatGPT, Claude, Hermes, and OpenClaw? Clanker exposes hosted Workspace MCP with browser OAuth for compatible clients. Follow the client-specific guide and verify status and tool discovery on your installed version. Connecting tools is distinct from hosting the agent itself. ### Does my assistant subscription cover Workspace compute? The external client’s subscription and model usage are separate from Clanker-hosted usage. Check the current Clanker plan and the charges for the work you authorize. ### Can I switch assistants without losing the Project work? Successfully saved Project files remain available to a later authorized task. Save a handoff with current sources, outputs, and open questions before switching clients. Private conversations in different clients do not synchronize automatically. ## Sources - [Clanker: connect an external agent and review permissions](https://clankercloud.ai/workspace-agents) - [Clanker: current agent instructions and access contracts](https://workspace.clankercloud.ai/for-agents.md) - [Clanker: current native tool schemas and availability](https://workspace.clankercloud.ai/workspace-tools.json) - [Clanker: native Agents, external clients, and execution ownership](https://clankercloud.ai/learn/native-agent-vs-external-agent) ## Related - [An agent space with a place for the next step.](https://clankercloud.ai/learn/ai-agent-space) - [Give your agents a place to do lasting work.](https://clankercloud.ai/learn/ai-agent-workspace) - [An agent runtime with a task you can inspect.](https://clankercloud.ai/learn/ai-agent-runtime) - [Keep ChatGPT. Build on the work.](https://clankercloud.ai/learn/use-chatgpt-with-clanker-workspace) - [Keep Claude. Give the work a home.](https://clankercloud.ai/learn/use-claude-with-clanker-workspace) - [Give Hermes Agent a Workspace for lasting work.](https://clankercloud.ai/learn/use-hermes-with-clanker-workspace) - [Give OpenClaw a Project and checked outputs.](https://clankercloud.ai/learn/use-openclaw-with-clanker-workspace) [Open Workspace](https://workspace.clankercloud.ai) [Current pricing and usage](https://clankercloud.ai/pricing)