Clanker CloudThree parts organize work in Clanker Workspace. A Project holds related context. A Session is the conversation where you work toward a result. An Agent is the assistant you select, with its own role and capabilities.
Understanding their jobs helps you decide what to keep together and what to reuse. You do not need a new Agent for every conversation, or one conversation for every piece of work a client will ever request.
Choose a Project around shared context
Consider a fictional business preparing a product launch. Its launch Project contains the approved brief, product facts, audience notes, and review criteria. Those inputs support several outputs: a website outline, a sales presentation, and a customer announcement.
The Project has a useful boundary because the work draws on the same background. A separate client launch should usually have its own Project, with that client's sources and instructions. Projects can also be organized into groups when you have several ongoing bodies of work.
General provides a starting place for everyday tasks. Move toward a named Project when the next task will need the same files, instructions, or decisions. The file organization guide helps define which source versions are current.
Choose a Session around a result
Within the launch Project, start a Session for the website outline. Keep revisions to that outline in its conversation. Start another Session for the sales presentation when you want its progress and feedback recorded separately.
This arrangement makes it easier to find the discussion behind each deliverable. You can return to the Session that produced the outline without scrolling through every slide revision and announcement draft.
For example:
| Work to do | Where it belongs | What to name explicitly |
|---|---|---|
| Draft the website outline | Outline Session in the launch Project | Approved brief and product facts. |
| Revise the outline's opening | Continue the outline Session | The section to change and the reason. |
| Prepare sales slides | New presentation Session in the same Project | Reviewed outline and intended audience. |
| Work on another client's launch | That client's Project and Sessions | Its own source packet. |
A fresh Session should receive a clear handoff. Identify the saved result and source files it needs. Project organization keeps context available; you should still make the intended inputs unambiguous instead of assuming that every earlier conversation is automatically the next task's evidence.
Choose an Agent around a reusable role
An Agent carries a method and selected capabilities. A proposal reviewer, concise writer, or research assistant can serve more than one Project if its role fits the task.
Keep launch-specific facts in the launch Project. Keep reusable writing rules in the Agent. For example, “Preserve uncertainty and cite factual claims” can apply across clients; “This launch is scheduled for Friday” is a changing Project fact.
You can start with an available Agent and create a custom Agent after you recognize a repeatable job. Selecting a role is separate from granting access to a connection or enabling actions. Check the actual files and capabilities available to the Session.
Test the arrangement with a small handoff
After reviewing the fictional outline, ask for it to be saved in Project Files. Open the saved file, then begin the presentation Session with:
Use the reviewed launch-outline.md and approved product brief. List the inputs you can access, then propose a five-slide structure for the sales team. Keep unresolved launch dates visible. Do not draft the full presentation yet.
The input list should match your intention. If it identifies an old draft, correct the source selection before continuing. A clear Project, a focused Session, and a suitable Agent give the work a structure you can understand when you return to it.
Sources
Give your assistant one useful job
Keep current sources, working drafts, and reviewed results easy to identify.