Clanker CloudYou have a useful conversation with Claude, produce a client brief, and then need to use that work again next week. The difficult part is often finding the current files and remembering which decisions were settled. A second assistant should not have to reconstruct the project from screenshots of the first conversation.
Clanker Workspace gives that work a home. A Project holds related files, instructions, Sessions, and outputs. You can work in its browser interface, connect a compatible external assistant, or build a custom Clanker Agent for a repeatable job. The point is to keep the evidence and result available when the conversation moves on.
Take the Workspace tour to see those surfaces together. The Projects, Sessions, and Agents walkthrough helps you choose where a new task belongs and what to carry into the next conversation.
Start with the dedicated Claude Workspace guide or ChatGPT Workspace guide. Each explains the connection, a concrete first deliverable, and how to leave a saved handoff for the next task.
Choose a first project from the invitations: a client kickoff with Claude, a weekly review with ChatGPT, or a research brief with Gemini. The agent handoff invitation gives other compatible clients a starting task and explains the MCP and native HTTP routes.
Keep the project useful to the next agent
Consider a fictional design studio preparing a launch proposal. Its Project could contain a client brief, a scope checklist, a draft proposal, and a note recording the decisions still awaiting approval.
Claude might read the brief and prepare a recommendation. Another permitted agent could review the saved recommendation against the checklist. The handoff works because both can use explicit source files and inspect the result, rather than because the two assistants automatically share memory.
Give files understandable names and record which version is current. Project instructions can explain the audience, output format, and how to treat missing information. A saved decision note is more dependable than assuming an assistant remembers a conversation you have not supplied.
The Project files guide covers the working structure. Keep confidential client material in the appropriate Project and account access arrangement.
Choose how your agent connects
There are four useful routes into the work:
| Route | What it gives you | What to check |
|---|---|---|
| Workspace MCP | Your external assistant calls approved Workspace tools from its own client. | Client compatibility, browser authorization, and granted permissions. |
| Native HTTP API | An agent with terminal and network access uses the documented account APIs to read and save native Workspace data. | The live API contract and a separately approved private account session; MCP tokens are not account cookies. |
| Bring your own agent, or BYOA | A supported agent runtime is registered with a Project and can be messaged or tagged in its Sessions. | Availability for your account, supported host, ready connection, and provider sign-in. |
| Custom Clanker Agent | A reusable specialist configured in Workspace with instructions, knowledge, Skills, and selected Tools. | Its role, capabilities, and behavior on a known example. |
For Claude's remote connector, begin with the Workspace MCP setup. OpenClaw, Hermes, ChatGPT, and other clients have their own compatibility and setup requirements; the external agent guide lists the supported connection details. An MCP connection grants tools to the assistant you are already using. It does not import every past conversation or merge provider accounts.
For a worked file task, try the OpenClaw supplier research walkthrough or the Hermes project handoff. Each starts with a read of known files before adding editing access.
BYOA is a separate setup. Where available, it can connect supported cloud runtimes, an enrolled computer, or a compatible existing host. Claude Code uses its own provider credential or native sign-in on a computer or agent host; hosted Claude Code installation is unavailable in the current preview. Check the BYOA guide for the selected runtime. Native BYOA harnesses are not currently run by regular Channels, Loops, or Schedules.
Try a small handoff
After connecting an external assistant, start with read access and ask:
Find my launch proposal Project. Read the client brief and scope checklist. Tell me which files you used, which proposal terms are supported, and which questions still need a decision. Do not edit files or contact the client.
Once that works, approve the editing access needed to save a review file. Before changing data through MCP, the assistant should follow the current managed Session instructions, record public progress, read back the result, and complete the task. Open the result in Workspace and check it against the brief. Another connected assistant can then read that exact file for its next task.
Access is governed by the granted permissions and the connected user's existing role. Workspace MCP permissions can apply across that user's accessible Workspace; do not assume the connection is limited to the single Project named in a prompt. Manage and revoke external access from Workspace agent connections.
Turn a good method into your own Agent
If proposal review becomes a weekly job, save the method in a custom Agent. Its instructions can specify the checklist, the output structure, and when to ask for a missing term. Keep each client's changing facts in its Project. The proposal-review Agent walkthrough provides a concrete starting role.
For recurring work or managed email, use a hosted Workspace Agent and the relevant setup. A connected Claude conversation does not itself create a background Schedule or an email worker. The business automation guide explains how to move a tested task into those workflows.
External model calls remain with the external assistant's provider. Clanker-hosted inference, compute, and paid tools use the authorizing user's Clanker credits at applicable rates. Check pricing and usage before enabling continuing work.
Sources
Give your assistant one useful job
Keep using your preferred assistant while giving it approved access to Projects, files, and saved work in Clanker Workspace.