Agent wakeups and schedules

Waking an agent appends a proactive turn to its lifetime conversation. The trigger does not bypass the normal model, tool, budget, event, or permission path. An accepted wake is a normal agent run.

Agent-owned background work uses the agent creator's effective no-training preference, plus any organization requirement. This applies to manual wakeups, scheduled wakeups, auxiliary calls, and sub-agents. If the coworker has received automation results, those creators' no-training selections also protect later work that may reuse the results.

d5s has one scheduled-work system. A scheduled wakeup can be a broad routine check-in, a named recurring responsibility, or an exact one-time reminder.

Trigger	Prompt	If the agent is busy	Schedule effect
Manual wake	Routine check-in	No-op: returns already running	Does not move a schedule
Scheduled wakeup	Its own saved prompt	Retains the due occurrence for retry	Completes once or advances after acceptance

Finish agent creation before configuring or testing wakeups. A draft may already have an inbox or connected channels, but it cannot run until activated. Timing or trial requests made during conversational setup are saved for later review; setup does not create a schedule or execute a trial task.

Manual wakeup

Use Wake now when you want an immediate proactive check-in. The agent is asked to review what changed in its project, act within its standing instructions, and reply tersely if nothing needs attention. It can use the workspace connectors currently enabled for its home project; turn off any connector that autonomous work should not reach.

A manual wake does not reset or advance any scheduled wakeup. If the session is already active, the wake is a no-op because the agent is already working. If today's daily budget is exhausted, d5s refuses the wake until the next local day.

Scheduled wakeups

Every scheduled wakeup has its own name, instructions, timing, state, and optional delivery destination. Telegram teammate DMs support incoming-message replies only and cannot receive scheduled deliveries. Choose a supported connected destination when the result should be sent outside d5s; the run's response also remains in the agent conversation.

Create and manage wakeups under Manage agent → Autonomy → Scheduled wakeups. You can also ask the agent to create, move, pause, or remove its own wakeups.

Choose Once for an exact date, time, and timezone. Choose Recurring for every 15 minutes, hourly, every 6 hours, daily, or weekly. A weekly wakeup can select any combination of Monday through Sunday, so one wakeup can cover weekdays, weekends, or another weekly pattern. A recurring wakeup can start immediately or on a chosen date, and can continue indefinitely, end on a date, or stop after a chosen number of successful runs. The editor previews the next occurrence before you save.

A chosen start date delays the first fire without changing the cadence. The first run is the first aligned occurrence at or after that start. A daily 09:00 wakeup starting on Monday therefore first fires at 09:00 on Monday, not at midnight.

A weekday selection belongs to the weekly cadence. Moving a weekly wakeup to any other cadence drops the selection and keeps the local time of day, so a Monday-to-Friday 08:00 wakeup moved to daily then runs at 08:00 every day.

Selecting an existing wakeup opens the same editor in place. The enable toggle and delete action remain separate from editing. Completed one-time and finite recurring wakeups remain visible with their completion state. An agent can have up to 21 wakeups.

If a transient error or an active run prevents acceptance, d5s retains that due occurrence and retries it. Once accepted, a one-time wakeup completes and a recurring wakeup advances. A recurring wakeup also completes after its final allowed run or when its next occurrence would fall beyond its end date. A budget-skipped recurring occurrence advances without counting toward a run limit. A budget-skipped one-time wakeup stays due and retries when budget becomes available.

How the agent manages its own wakeups

Ask the agent to create, list, change, pause, or cancel its wakeups. Pausing keeps a wakeup visible so it can be enabled again; cancelling removes it.

Asking the agent to create a wakeup with the same name as an active one replaces that wakeup's instructions and timing and restarts its run history. Its delivery destination stays the same unless you request a change. Retrying the same creation request does not add a duplicate.

Wakeups can deliver only to supported destinations connected to the agent. Changing a wakeup from the app requires permission to manage that agent.

You can ask the agent to manage its wakeups from d5s or a connected channel. Its ordinary schedule limits and permissions still apply.

Cost boundary

Every accepted wakeup starts model execution. Frequency, accumulated context, model choice, reasoning level, sub-agents, research, and connector calls therefore affect cost. Connector availability alone does not start a call.

The agent's daily budget is a hard cap across manual and autonomous work. It resets at midnight in the agent's budget timezone. A budget skip adds at most one notice to the conversation per local day, and scheduled work resumes automatically on the next day unless the agent is separately paused.

Automation findings

An attached automation runs with its own context and queues a one-time internal notification when the run ends. In Automation team, Keep informed asks the agent to acknowledge the compact result unless a standing user instruction already calls for follow-up; Act on findings asks it to assess and follow up on actionable findings under existing permissions and approval rules. The receiving agent performs authorized follow-up using its own context and tools; the automation remains independent. Both modes wake the agent without waiting for a human message, subject to its pause, active-work and budget settings. The agent receives a bounded excerpt and can inspect the referenced result under current access and model privacy rules. This setting does not authorize external messages or change the agent’s ordinary approval requirements.

An agent can choose either mode for itself or stop following an automation. Stopping suppresses linked automation notifications that have not started; changing to Keep informed also suppresses unstarted attention wakeups. Already received results and running work remain in its conversation. Other scheduled wakeups are separate from these subscription settings.

Some older automation reminders were saved as ordinary agent wakeups. Those reminders need to be canceled separately under Manage agent → Autonomy → Scheduled wakeups. Stopping an automation subscription cannot identify or cancel them automatically.