Files and artifacts
Files are the material Gideon works with. Artifacts are outputs you can inspect and use. In hosted Gideon, the workspace belongs to your remote runtime.
Bring the right material
Attach a file to a conversation or use the Files surface. Tell Gideon which file is authoritative and what it may change. A path on your browsing device is not automatically a path in the hosted workspace.
For reference material you want to find again, add it to Knowledge. Files, saved knowledge, and chat attachments serve different purposes; say which source to use.
Ask for a bounded change
Inspect this CSV and report its columns, row count, missing values, and duplicate records. Then summarize [question] with the calculation behind each result. Save a new output file; keep the input unchanged.
Review an artifact
Open the artifact from the result or Artifacts. Check that it contains the requested output. For code or an interactive artifact, distinguish a rendered preview from a tested application. For a document, check links and any export you intend to share.
Find a missing result
Ask for the exact saved path or artifact link. If the result exists only as text in chat, request that it be saved. If an attachment cannot be read, check format and size, then provide a supported version or paste the relevant excerpt.
Do not upload credentials as ordinary task material. Use Connections for service secrets.