Inspect task results

A NextClaw task can deliver more than a chat reply. It may produce explanations, files, source code, Markdown, charts, HTML pages, images, or a Panel App.

Where results appear

Session content

Use the conversation for conclusions, status, and questions that need your decision. Important claims should point to a file, source, or concrete number.

Session workspace

The right workspace exposes project files, open files, subtasks, and scheduled jobs related to the session. Generated files should also exist in the agreed output directory.

File previews

Open Markdown, code, HTML, documents, spreadsheets, and presentations without leaving the task. HTML can be inspected as source or rendered output, and code changes can be reviewed as diffs.

Panel Apps

Dashboards, forms, calculators, and interactive pages can remain available as Panel Apps instead of becoming a static screenshot.

Review checklist

1. Goal: does the deliverable answer the original request?
2. Inputs: were the right files, links, and date ranges used?
3. Actions: did it avoid unintended overwrites, deletions, sends, or external requests?
4. Output: do files open, numbers reconcile, and pages work?
5. Boundaries: are sources, limitations, and uncertainty visible?

Refine the result

Name the existing object and the requested change:

Keep the processed data. Replace the first page with an executive summary and add the data refresh time.

Review the actual final file after the change. Do not treat a textual success message as proof that the artifact is correct.

Next: choose how to reuse the work.