Bots

Bots are the teammates. Each one has a name, a role, and memory — chat with them in the roster, hand off jobs, and come back to finished results.

The roster

The left sidebar lists every Bot on your team. Selecting one opens its conversation; unread work and pending approvals surface there. Your first Bot, Wayfind, is a chief of staff seeded automatically — a good default for anything you haven't assigned yet.

Creating a Bot

Create a Bot with a name and a role that describes its job — “Aria, bookkeeping” beats “Assistant”, because the role shapes how it works and what it remembers. Pick a color and shape so you can spot it at a glance.

One Bot per job works best. A bookkeeping Bot and a support Bot stay sharper than one generalist trying to do both.

Memory

Bots remember your workflows across conversations: how you like invoices reconciled, which mailbox is support, what “the weekly report” means. Corrections stick — tell a Bot once and it applies from then on.

Conversations

Every Bot keeps its own conversation history. Ask follow-ups in the same thread and the Bot keeps context; start fresh any time. Long-running work continues in the background on your cloud computer — close the laptop, come back to the result.

Background work

Bots can run routines on their own and check in when they need you. Anything sensitive — sending, paying, publishing, changing important records — pauses for your approval first. See Cloud computer for where this work runs.