Conversation

A task isn’t “assign once and you’re done” — it’s an ongoing collaboration. You can ask follow-ups, add notes, or upload new materials at any time, and Aureink keeps working with the earlier context. This page covers how to collaborate with it while it runs.

1 · How the conversation works

Type your request or additional notes right in the input box, and Aureink keeps working based on the earlier conversation context — you don’t need to restate the background.

〔Figure: Main conversation area, marking the input box and top actions〕

2 · Sending messages & follow-ups

• Keep following up: If you’re not happy with the current result, just say “make it more concise,” “turn it into a table,” or “add the third-quarter data.”
• Add context: Append new files, requirements, or preferences at any time.
• Structured clarification: When information is missing, Aureink asks you back, offering options or fill-in fields so you can add detail, then continues once you answer.

〔Figure: Example of a structured clarification prompt〕

3 · Uploading files & images

Aureink often needs your materials to work on a task. Three ways all work:

1. Click the + menu → Attach file, and choose a local file or image;
2. Drag a file directly onto the input box;
3. Paste a file or long text from the clipboard (long text becomes an editable reference snippet).

Supported file types: common documents, spreadsheets, slides, PDFs, images, text/code, and more.

Privacy & authorization boundary: Aureink only handles files you actively upload or authorize in a workspace; it won’t scan other directories on its own. Please upload only the materials this task needs.

4 · What execution shows

While a task runs, the main area shows in real time what Aureink is “thinking and doing”:

• Thinking trace — its reasoning process.
• Tool calls — reading/writing files, running commands, web searches, and more; expand to see each call’s input/output, time taken, and whether it succeeded.
• Sub-task — complex tasks split into sub-tasks that run in parallel.
• Charts & previews — if a generated Mermaid diagram has a problem, one click runs “AI fix.”

〔Figure: Thinking trace with tool calls expanded〕

5 · Interrupt, retry & restore

You always keep control over the execution:

• Stop generating — interrupt the current run at any time.
• Retry / resend — retry a given reply, or edit and resend it.
• Restore files to this point — roll back the local file changes made by a given AI turn to the state before it, so mistaken edits are no problem.

〔Figure: The “Restore files to this point” action on a message turn〕

Notes & key reminders

• Sensitive operation confirmation: Writing/deleting files, running commands, going online, and similar actions request confirmation according to the current permission mode.
• Restore scope: Restoring applies to local file changes; messages already sent to external channels can’t be recalled.
• Quota usage: Every follow-up and run consumes usage quota.

Last updated · July 2026 ｜ Next: Task management →