Skip to main content
When you open a task in the workspace, the chat pane gains a task channel. Messages you send here are scoped to that task — the agent automatically receives the task’s title, status, template fields, and linked documents as part of every turn.

​
Per-Task Conversations

Each task has its own channel. The conversation persists with the task — if you close the task and reopen it tomorrow, the history is still there. This makes the channel a natural log of “what was discussed and decided while completing this task”. Switching between tasks switches the channel. The agent’s project-level knowledge is unchanged, but the task in scope changes.

​
What The Agent Knows About The Task

Without any prompting, the agent has access to:
  • The task’s title and description.
  • The task’s status in the template’s status flow.
  • The task’s template fields — which fields exist and what the current values are.
  • Linked documents — references to any documents attached to or produced by this task.
  • Any extracted data the upstream pipeline has populated.
You can confirm what the agent sees by asking: 
What's this task about, and what do you currently know about it?

​
Common Task-Channel Prompts

Help me complete this task.

What fields are still missing from this task?

Show me the extracted invoice data on this task.

Compare the extracted total against the line item totals — do they match?

Mark this task as ready for review.
The agent answers using the current task context. Where it needs to update fields or change status, it will tell you what it intends to do and apply the change atomically (status changes are not drafts).

​
Task Channel Or Project Channel?

A useful rule of thumb:
  • Task channel — anything about this task: completing it, reviewing its fields, comparing its data, transitioning its status.
  • Project channel — anything that affects the project as a whole: editing the activity plan, changing the task template, adjusting bound resources.
If you find yourself asking the agent to “update the task template so that…” from a task channel, the change you are about to make is project-wide. Switch to the project channel so the change is scoped correctly and the conversation lives where future readers will look for it.

​
The Agent Can Read Linked Documents

When a task has documents attached, the agent can read them. Ask: 
What's the vendor name on the attached invoice?

Open the invoice and focus on the line items table.
The first is a reading question — the agent inspects the document and replies. The second triggers a UI command: the agent opens the document in the workspace and scrolls to the line items. See UI Interactions for the full set of UI-driving behaviors.

​
A Worked Example

A reviewer opens an invoice review task and asks: 
Walk me through what extraction found, what's missing,
and what I need to verify before I approve.
The agent responds with a short summary, lists the fields that are populated and any that are flagged as low confidence, opens the original invoice document, and focuses the first low-confidence field. The reviewer reads the on-document evidence, confirms or corrects, and then: 
Set the status to "Approved" and add a note that line items were verified manually.
The agent updates the status and posts the note to the task. The whole exchange is preserved in the task channel — anyone who comes back to the task later can see exactly what was checked and decided.