Sessions

A session is one conversation with a colleague. You can have as many open as you want — different colleagues, different topics, all running at the same time. Sessions are persistent. Close the tab today, reopen the same chat next week, the history is still there.

​

Sessions run in parallel

You don’t wait for one colleague to finish before talking to another. Open six chats with six colleagues; they all work in parallel. The same colleague can run multiple sessions at once. Sofia can be writing a sales summary in one chat while she’s drafting outreach in another.

​

They stay in sync

Open the same session on your laptop and your phone, both update in real time. If a colleague writes a paragraph in one tab, it shows up in the other. Pause a colleague from your phone, the desktop reflects it. This matters most for long-running work. Kick off a research session before a meeting. Jump back to it from another device after. The colleague is still there, with the same context, ready to keep going.

​

Pause anytime

If a colleague is going down the wrong path, pause them. They stop, you see what they had so far, and you can:

• Type a new instruction to redirect them.
• Resume from where they were.
• Just close the tab — the session is saved.

​

Side effects of a session

Beyond the chat itself, a session can produce:

• Files — drafts, reports, charts, spreadsheets, code. They land on the colleague’s hard disk.
• Views — live dashboards. The colleague builds them inline or saves them to your views page.
• Jobs — if you ask them to do this every Monday at 8am, the session becomes a recurring job.

A session is the start of most things. The other concepts are what comes out of it.

​

Where to next