Skip to main content
Every job you hand a coworker is a session: one conversation, its own files, its own history. Each coworker lists your sessions with it on its Sessions tab, most recently active first.
A few places in the app still say “task” for a session, such as the workflow step that hands work to a coworker. It’s the same thing.

Running several at once

Your coworkers work in the background, so there’s no reason to wait. Start a research session, leave it running, and start something else. Come back when the first one’s done. Sessions are yours. Other people in your workspace have their own, even when you share a coworker — so a colleague giving Nora a job doesn’t interrupt yours.
A list of tasks showing the coworker, the title, a status of working, needs you, done or idle, and how long ago

Everything in flight, and which coworker has it. The one to look at first is always "needs you".

Starting a new one

From the header of any session, or with /new. Start a new session when the job is genuinely different — not just because the last one got long.
One job per session. Related follow-ups belong together; a new subject deserves a new session. It keeps each conversation focused and stops long conversations filling up prematurely.

Coming back to one

Open any session and it’s exactly as you left it — the conversation, the files, the steps it took. Send a message and your coworker picks up with everything it knew. You don’t re-explain. This is why “actually, also do X” works days later.

Marking one done

There’s a Mark session done control in the header for tidying up. It parks the session rather than closing it for good:
Session closed Send a message to re-open it.
That’s deliberate. Work you thought was finished often isn’t, and a session you can revive with a message is more useful than one you have to recreate.
A session that ends naturally isn’t closed either — your coworker posts a wrap-up and stops. Marking done is for tidiness, not for finishing.

Choosing the right coworker

Give a session to the coworker whose job it is. A research question to the researcher, an inbox to the assistant. If you’re not sure, pick the closest and let it hand the work on. It can ask another coworker in its agent rather than doing an unfamiliar job badly. The other coworker’s session shows up in your list too, titled with who asked, like For Sam: Research Northwind’s last quarter….

Good to know

Give the session a clear first message. It becomes how you recognise the session in a list later, and a session called “Untitled session” is one you’ll never find again.
Files belong to their session. A file from one session isn’t visible in another. To keep something around, save it to the coworker itself — see Files overview.

Common questions

Enough for real work. If several are running they simply proceed in parallel — you don’t have to sequence them.
Not directly. Either start a new session with the right coworker, or let the current one hand off the part it can’t do. Type @ and pick a coworker to name who it should go to.
No. A session that isn’t running isn’t doing anything. Keep them.
Sessions are private to whoever created them, even when the coworker is shared.
Stop the session first for a clean finish. Pausing stops new work rather than tidying up work in flight — see Retiring and re-hiring.

Next steps

The conversation

Working inside a session.

Long conversations

When one runs long.

Your coworkers at a glance

The wider view.

Schedules

Sessions that start themselves.