Auto Mode

Each task has a status. The bot moves it from one status to the next as it works through the task; you can also move it by hand from the dashboard.

• PENDING— not started. The next fire of the goal's or task's schedule will pick it up.
• IN_PROGRESS — the bot is working on it right now.
• COMPLETED — the bot finished successfully. On completion the bot writes a PROGRESS entry to the diary and moves on to the next task.
• FAILED — the bot hit an error it could not work around. If reflections are enabled and the failure streak hits the configured threshold, the bot runs a reflection turn to recover.
• SKIPPED — the task no longer makes sense (a parent failed, the situation changed, the task was deliberately skipped).

Re-running a completed task from the dashboard resets it to PENDING; the next fire of its schedule picks it up and moves it to IN_PROGRESS. Diary entries of all five types — THOUGHT, PROGRESS, OBSERVATION, DECISION, ERROR — are written by the bot during task execution; only the PROGRESS on completion is automatic.

Open Settings → Auto Mode in the dashboard. The card on this page is the primary place to configure Auto Mode — leave the defaults alone for the first run, then revisit as you learn what you need.

Open Goals & Tasks in the dashboard sidebar. The page has two panels: a Create goal or task card on the left and a list of existing goals and standalone tasks on the right.

On the create card, flip the type toggle between Goal and Task. Both share the same fields:

• Title — required. Shows up everywhere.
• Details — optional free-form notes for you, not for the bot.
• Prompt — optional instruction the bot follows when the task runs. Falls back to the title when left blank.
• Reflection tier — optional per-item override for the tier used during reflection turns.
• Reflection priority — when checked, the per-item reflection tier wins even if an active skill declares its own.

Tasks also carry an Attach to goal dropdown. Pick a goal to make the task part of it, or leave it on No goal (standalone task) for one-off jobs.

Click Create goal or Create task. The new item appears in the list on the right with status, progress badge, details, prompt, and three actions on each row:

• Schedule — jumps to the Scheduler page with the goal or task pre-selected.
• Edit — opens a modal to change any field. Save or Cancel.
• Delete — removes the item. Tasks nested under a goal are deleted with the goal.

A goal can be put on hold by editing it and setting its status to PAUSED; the schedule keeps ticking but the runtime skips non-ACTIVE goals. Flipping it back to ACTIVE resumes work on the next fire.

Open Scheduler in the sidebar. The left panel is a Create schedule card; the right panel is the Schedules table with one row per schedule.

On the create card, pick a target type (Goal or Task), then choose the specific goal or task from the dropdown. Below that is a mode toggle: Simple or Advanced cron.

• Simple — pick a frequency (Daily, Weekdays, Weekly, or Custom days), toggle the days if needed, and set a time in HH:mm. Presets for 09:00, 12:00, 18:00, 21:00 sit next to the input. All times are UTC; the card shows your browser timezone for reference.
• Advanced cron — paste a cron expression or pick one of the presets (* * * * * every minute, */5 * * * * every five minutes, 0 9 * * MON-FRI weekdays 09:00). Five fields (min hour day month weekday) or six fields (sec min hour day month weekday) — the runtime uses Spring's cron parser, not Quartz, and fills in a leading 0 for seconds when you give five fields. Times are UTC.

The rest of the form applies to both modes:

• Repeat limit — how many times this schedule fires before it stops. Presets for 1, 3, 5, 10, and Unlimited. Required.
• Clear context before run — wipe the agent session before each fire, so every run starts with a fresh context. Off by default.
• Report channel — where milestone and error notifications go. Pick a channel type (Telegram, Discord, webhook, email) and fill in the target. Optional; leave blank for silent runs.
• Enabled toggle — shown only on the edit form. Lets you pause a schedule without deleting it.

Click Create schedule (or Save schedule when editing). The row appears in the table on the right with the target, cron, runs count (2 / 5), next fire time, and action buttons — Logs, Edit, Delete.

The diary lives behind the Logs button on each row of the Schedulertable — not on the Goals & Tasks page. Click Logs and a modal opens with two panes.

• Recent runs (left) — every run recorded for this schedule. Each entry shows its timestamp, run ID, status, message count, and the task it touched. Click a run to select it.
• Transcript (right) — the full conversation for the selected run: user turns, assistant replies, tool calls, and the model tier and skill used for each message. This is where you read what the bot thought, observed, and decided on that run.

The bot also runs a 1-second scheduler tick under the hood; on every tick it collects all schedules whose next fire has arrived and executes each of them in turn. Several schedules can fire back-to-back in the same tick when they line up — one run per schedule, not one run per tick.

Every Auto Mode surface is also reachable from chat. These commands are meant for quick adjustments during a conversation, not for initial setup — for day-to-day configuration, use the dashboard.

• /auto — toggle autonomous mode on or off for the current session.
• /goal — create or update a goal inline.
• /goals — list goals and their status.
• /tasks — list tasks for the current goal or across all goals.
• /schedule — attach a schedule to a goal or task from chat.
• /diary — print recent diary entries in the chat.

The bot itself manages goals and tasks through the goal_management tool when it is planning — the same operations the dashboard and chat commands expose, but driven by the model instead of you.

Goals, tasks, schedules, and diary entries all survive container restarts — they are persisted to auto/goals.json, auto/schedules.json, and auto/diary/<date>.jsonl in the workspace and reloaded on boot. If Auto-start on startup is on, the scheduler resumes firing as soon as the bot comes back up. A goal paused before the restart stays paused; resume it from the dashboard when you are ready.