ClankerClanker Workspace
How work moves through Clanker Cloud.
Start a Session with an outcome and source material. The selected Agent uses available files and tools, records progress, and returns a result for review. Projects preserve related context; recurring workers and computer environments are configured when the task needs them.
Start with $20 in included credits. See usage and plans.
1. Give the work context
Create or select a Project, add files, and state the result you need. Project instructions can hold the preferred format or process. A Session focuses the conversation on a particular output.
For example, a vendor review can start with three proposals and a procurement checklist. The Agent should compare the source material and flag missing terms instead of assuming every proposal contains equivalent information.
2. Choose the tools and environment
A normal Session works with research, writing, Project files, and selected tools. Cloud browser adds website interaction; cloud compute supports scripts and file generation. Remote Connection is a separate path to an explicitly connected computer.
Choose only the access needed for the task. Availability and permissions are visible in Workspace. Instructions describing a task do not establish that an external account or computer has been connected.
3. Review the work and the saved output
Use Ask to review changes first. Notify and AUTO change the approval experience; AUTO approves enabled actions. Inspect the result itself using Preview or the Project’s Files tab, not only the summary in the conversation.
Ask for corrections where source facts, calculations, or behavior are wrong. Check that the file opens and that an App’s main actions work before sharing it. Keep the sources with the result for later review.
4. Reuse what proved useful
Make an Agent for a stable role, keep a method as a Skill, or use a Tool for an operation you repeat. For recurring work, test one run before configuring a Loop or Schedule.
Review progress and usage in the worker history. Stop unused environments and recurring jobs. Work on a connected computer requires that computer to remain available; hosted execution and local device access have different boundaries.
Common questions.
What is the difference between a Project, a Session, and an Agent?
A Project keeps related files, instructions, and work together. A Session is a conversation where work happens and progress is recorded. An Agent is the assistant doing the work, with its own instructions, skills, and selected tools.
More in the FAQHow do I control approvals?
Session settings include Ask, Notify, and AUTO. Choose Ask when you want to review changes first. AUTO approves all enabled actions, so check the Agent’s access and capabilities before using it.
More in the FAQCan it work while my laptop is closed?
Hosted Loops and Schedules can run recurring work in the cloud. Tasks using a connected computer still need that computer to be online and available. Simply starting a browser conversation does not turn it into a recurring background task.
More in the FAQSources: Workspace guide: start a useful Session · Workspace guide: choose an environment
Content reviewed against the Workspace Guide & FAQ. Features and access can depend on your account.