> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cogniagent.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The conversation

> Working with your AI coworker is a conversation, not a form. Here's what's on screen and how to steer it while it works.

You ask, it works, you watch. You can step in at any point without stopping it.

## What's on screen

Three things, and you'll use all of them.

**The conversation** in the middle — your messages, your coworker's replies, and every step it took in between. Nothing is hidden; if it opened a file or searched for something, that's a row you can expand.

**The files panel** beside it — everything in the task. Anything your coworker produces lands here. See [Files](/cowork/files/overview).

**The message box** at the bottom, which does more than it looks like. `/` opens the [command menu](/cowork/chat/slash-commands), `@` points at a file, and the paperclip attaches one.

<Frame caption="Two files attached, and the controls that shape the answer — mode, effort and model — sitting under the box.">
  <img src="https://mintcdn.com/glorium/JBtd_griZWPnHu68/images/cowork/chat/overview/01-composer.webp?fit=max&auto=format&n=JBtd_griZWPnHu68&q=85&s=7040f35a45bf0055e13ef6f6bf81c886" alt="The message box with two attached spreadsheets and the plan, effort and model chips beneath it" width="1280" height="268" data-path="images/cowork/chat/overview/01-composer.webp" />
</Frame>

## Asking well

The single biggest difference in output quality comes from the first message.

**Say what you want to end up with.** "A one-page summary I can send to my boss" produces something different from "look into this".

**Attach the real thing.** Upload the export rather than pasting three rows of it.

**Say what you already know.** Saving your coworker from re-deriving context you have is free speed.

**Say what to avoid.** "Don't email anyone" is worth writing if that matters.

<Tip>
  You don't need to be precise on the first try. It's a conversation — say "not quite, more like this" and it adjusts, without starting over.
</Tip>

## Steering while it works

You don't have to wait for it to finish before saying something.

**Type while it's working.** Your message is queued and picked up as soon as the current step settles. Queued messages appear above the box, and you can edit or cancel one before it's sent.

**Correct it mid-task.** "Stop doing it that way" lands and it adjusts.

**Stop it.** If it's clearly off track, stop it and re-ask. Faster than watching it finish something wrong.

## Finishing

When your coworker considers the job done, it posts a short wrap-up you can expand for the detail.

A finished task isn't closed. Send another message and it picks straight back up with everything it knew — which is why "actually, also do X" works without re-explaining. You can mark a task done from the header, and even then a new message re-opens it.

## Common questions

<AccordionGroup>
  <Accordion title="Can I close the tab while it works?" icon="power-off">
    Yes. It keeps working. Come back whenever and the whole conversation is there.
  </Accordion>

  <Accordion title="Will it ask before doing something significant?" icon="hand">
    Anything leaving your workspace waits for approval. See [Approvals](/cowork/control/approvals) and [Permission rules](/cowork/control/permission-rules).
  </Accordion>

  <Accordion title="What if I change my mind halfway?" icon="arrows-rotate">
    Just say so. Mid-task changes of direction are normal and it doesn't need to start again.
  </Accordion>

  <Accordion title="Should one task cover several jobs?" icon="list-check">
    Related work, yes — the shared context helps. Genuinely separate jobs are better as separate tasks. See [Managing your tasks](/cowork/chat/tasks).
  </Accordion>

  <Accordion title="Can I see what it actually did?" icon="eye">
    Every step is in the conversation and can be expanded. See [Watching progress](/cowork/chat/watching-progress).
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Slash commands" icon="terminal" href="/cowork/chat/slash-commands">
    Everything you can type.
  </Card>

  <Card title="Watching progress" icon="chart-line" href="/cowork/chat/watching-progress">
    Following the work.
  </Card>

  <Card title="Plan mode and Build mode" icon="compass-drafting" href="/cowork/chat/plan-and-build">
    Agree the approach first.
  </Card>

  <Card title="Attaching and mentioning files" icon="paperclip" href="/cowork/files/attaching-and-mentioning">
    Getting files into the conversation.
  </Card>
</CardGroup>
