Tasks and memory

How assigned work, repeating tasks, and your bot's context fit together

A Bot keeps several responsibilities going in one conversation. State the outcome and the sources it should use; you can add instructions any time, and its actions stay within the permissions described in Control your bot.

Assigned work

A Bot works when you message it and when one of its routines fires. It can split a job across sub-agents that run in parallel, and each run shows up under Recent activity in the details pane. Click a sub-agent to read its transcript in a viewer tab.

WorkWhere it runs
Browsing, shell and file workThe Bot's cloud computer
Files and shell on your machineThe desktop you allowed, with the app open
A routine runIn the cloud, posting into the Bot's own conversation

A Bot can also set itself to wake later and check on something. It can do that at most 24 times a day and tells you where things stand when it reaches the limit, and each time a check finds nothing new it waits longer before the next one. A report from the personal Bot's background research reaches it whole, however long it is.

Check outputs and errors even for runs that finished; see Review work.

Recurring tasks

A recurring job is a routine. Create one from the Bot's Routines list with Add routine on web and desktop, or New routine in Bot settings on iOS and Android. Each has a Name, an Instruction and a When to run setting, and a Bot can hold up to 20.

Timing options are Every hour, Every day, Weekdays, Every week, Every month, Interval (every 1 to 168 hours) and Advanced…, which takes a recurrence rule such as FREQ=WEEKLY;BYDAY=SA.

Each weekday, review the planning notes and tell me only when a deadline is at risk.

Switch a routine off with Active, or delete it from its editor. Routines are sorted by latest run, and a routine's runs open in a dialog. The first task of a run continues the routine's conversation, and other tasks get their own. Pausing the Bot stops all of its routines; see Controls. Scheduled runs happen on the server, so they continue while your devices are off.

Event monitoring

Instead of a clock, a routine can wake the Bot when a service sends an event. Choose Git event (GitHub), Linear issue, Sentry alert, PagerDuty incident, Webhook or Firecrawl Monitor. Slack message and Teams message are listed but not available.

An event routine gets its own webhook URL and optional signing secret once it is saved. Paste the URL into the sender, for example a repository's webhook settings in GitHub. Filters narrow what wakes the Bot: GitHub offers events, repository and branch, while Linear, Sentry and a plain webhook filter on event names. A routine uses either a schedule or an event, never both, and the event type can only be chosen when the routine is created.

Context and memory

A Bot draws on three sources: the conversation, your account memory, and its own learned memory.

Conversation context

The Bot's one continuous conversation is its working record. The model and reasoning level are fixed by ZeroTwo for every Bot, so a Bot behaves the same whether you message it, call it or a routine runs.

Persistent memory

A Bot sees your saved memories, Knowledge and recent chats, plus memory it has learned itself. That learned memory is scoped to one Bot, so a different Bot cannot see it. Your Memory settings under Personalization apply. Routine and wake runs can read memory but do not write new memories.

Across messaging channels

Memory is per Bot, not per channel: the same Bot uses the same learned memory in its own conversation, on a call and inside a group channel. See Message your bot.