Scheduled work

The daemon can run work while the app window is closed. It must be running and the computer must be awake when a job is due. Quitting an app-owned daemon stops its jobs; use an independent daemon if the desktop app should be able to quit. Turn on Scheduling in Bot settings, Tools, then start a new section and ask the bot to create the job.

Create a job in chat

Describe the task, timing, and result you need. For example:

Every weekday at 9am, read the notes in my workspace and write a short list of unfinished tasks. Save the result locally. Tell me the job ID and next run time.

The scheduler accepts intervals such as every 2h, a one-time delay such as in 30m, daily or weekday times, five-field cron expressions, and explicit timestamps. Wall-clock schedules use the daemon’s local timezone. If your client is elsewhere, confirm the next run time with the bot.

Jobs belong to the bot that creates them. By default, an agent job starts a fresh conversation using that bot’s configuration. It can also select a model or skills for the job. Provider usage is billed as usual.

Where results go

Scheduled output is saved locally, not delivered into the conversation that created the job. Output files live under profiles/<bot>/cron/output/ in the daemon’s data directory. Ask the bot to read the latest result or error for a named job.

Hexbot currently supports local delivery only. Do not rely on a reminder appearing as a chat message, email, or push notification. Ask the bot to confirm where it saved the result.

Manage jobs

In the mobile app, open Daemon, Jobs to create, edit, pause, resume, run or remove jobs. Bot settings also shows that bot’s jobs. The desktop and browser clients can manage jobs through chat. Ask the bot to:

List its jobs, including paused jobs, and their next run times.
Update a job’s prompt or schedule.
Pause a job, then resume it when needed.
Run a job now to check the output.
Remove a job you no longer need.

Use the job ID when two jobs have similar names. Deleting a bot also removes its scheduled jobs. Pausing a job preserves its definition.

Scripts and unattended access

A job can run a script in the bot’s scripts folder or workspace. Scheduling an absolute script path asks for approval. Scripts run read-only in Manual and inside the workspace sandbox in Auto or Bypass, without model provider credentials. On Linux, scheduled scripts need working bubblewrap.

An autonomous agent job and its delegates cannot wait for you to answer a question or approve a tool. Give the job enough detail and access to finish on its own. Actions that need approval are refused immediately; inspect the error before broadening access.

Jobs and memory

A job can read the bot’s memory and notes but not write them. When a job asks to add, replace, or remove a memory entry, or to note something, Hexbot saves the request as a proposal, and the bot’s next dream decides whether to keep it. This keeps text a job fetched from the web out of memory until the bot has looked at it with the rest of the day. See Dreaming. A job cannot change the bot’s soul either; the bot tells you when it wants a soul change, and you make it in a section.

For memory reviews, use Dreaming. Dreaming has its own controls and saves summaries in the bot’s dream log.

Jobs and their delegates run in Auto when the bot uses Bypass; Manual stays Manual. They cannot message other bots, because a recipient’s ordinary section could change memory without a dream reviewing it. Job results stay local.