Skip to content
Tusko Docs

Chat to artifact

Every task follows the same loop:

  1. Chat (fast, no sandbox). Describe the outcome in plain language, e.g. “Create a 6-slide Q3 deck with speaker notes.” The agent starts with plan_task: a named goal plus 3–5 concrete milestones shown inline.
  2. Lazy execution (sandboxed). When files or code are needed, the agent calls write_file (e.g. generate_slides.py) then execute_command (python3 generate_slides.py) inside an isolated OpenSandbox container. Office libraries — python-pptx, openpyxl, pandas, python-docx, pypdf — are pre-installed from the sandbox image, so generation starts immediately.
  3. Artifact (preview & download). Files generated by execution auto-surface as artifact cards in chat and in the Files panel. Uploaded files, parsed documents, and compare_files diffs render the same way.

Tips:

  • Sample starters live in the empty state: Sales presentation, Excel report, Client proposal, Compare two files.
  • Drag & drop files anywhere onto chat to upload them into the session workspace.
  • Start over clears messages but never deletes files; an Undo banner restores them.
  • Listing or reading workspace files never spawns a sandbox — only execution does.