Run your first task

Describe the task in a sentence, attach your material, and ClawsGO gets to work on a cloud host.

Write a good task description

No prompt engineering needed. Brief it the way you would brief a new colleague. Three parts:

Goal: what you want back (a review, a figure, runnable code).
Material: attach files or point to data sources.
Constraints: format, length, language, deadline.

Example

Using the 42 PDFs attached, write a systematic review on the stability of
perovskite solar cells. Around 8,000 words in English, organised into
degradation mechanisms / encapsulation strategies / testing standards.
Cite the source paper for every claim and finish with a comparison table.

The message body is capped at 32,000 characters. Anything longer goes in as an attachment.

Attach material

Three ways: "Upload files" in the "Add" menu of the composer, drag files onto the composer, or paste (screenshots included).

Up to 10 files per message. The per-file size limit depends on your plan, see Plans.
Uploads start as soon as you pick the files. You cannot send while an upload is in progress. Failed uploads offer "Retry" and "Remove".
Type @ to reference a file already in the task directory, and / for commands and skills.

What you can set before sending

The settings button in the composer shows the current model and reasoning level. It opens five groups:

Option	What it does
Mode	"Balanced" runs a single agent. "Cluster" orchestrates a group of subagents in parallel for heavy research such as surveys and reviews; it burns credits fastest. Pro and above
Model	See Choose a model
Reasoning	Low / Medium / High / Extra High / Max. Max may make the model overthink; if it runs too long, use High or Extra High
Context	256K or 1M, see Choose a model
Permissions	"Approval" always asks before sensitive actions; "Auto" only asks for detected risky actions; "Full access" runs any action without asking

Cloud hosts default to Full access, your own device to Auto. Any setting you change away from the default stays visible on the button.

Above the composer is the host and working directory selector. Tasks started inside a project inherit the project's host and directory and cannot change them.

Enter sends, Shift+Enter inserts a line break. The microphone button records up to 60 seconds of voice; the transcript is placed in the composer and is not sent automatically.

Every tool call appears on the timeline as it happens. While running, steps are expanded; once settled they collapse into a single line, "Worked through N steps", which you can open to see each step's input and output. The context bar above the composer shows how much of the window this turn has used; earlier conversation is compacted automatically as it fills.

Where the deliverables are

Output files live in the "Files" tab of the right panel. When ClawsGO delivers a Markdown, PDF or image file it opens a preview automatically and the right panel folds away to make room; close the preview and the panel returns. See Files and previews.

After that