Routines and Inbox

Use routines for recurring local work, such as reviewing project status or preparing a summary from notes. A routine records its agent, instructions, time zone, cron expression and execution ownership.

Configure a routine

Choose the intended agent and scope, review the schedule and enable it deliberately. Project-linked work additionally requires valid local project ownership. New ownership grants require connectivity; a previously confirmed owner can continue offline when its other dependencies remain available.

One routine does not overlap itself. Missed occurrences are coalesced into a reported catch-up run; already admitted work resumes before catch-up. Disabling a routine stops future admissions rather than relabeling its current work as cancelled.

The service host must stay running and awake. An installed phone/browser PWA does not run the server in the background. There is no offline browser mutation queue, event-triggered routine system or provider-spend cap.

Read the Inbox

The Inbox collects actionable questions/blockers and meaningful completed delegated work, scheduled results and findings. A routine that finds nothing new can remain only in run history. Ordinary chat replies and internal helper completions do not each create a result notification.

Viewing the actual result marks that revision read. History remains available. Questions and blockers remain until resolved, including after being read. A newer revision is not hidden by a late read acknowledgement for an older result.

Another host's work

Synchronized remote reports are historical observations. They do not provide live control of the other host or permission to cancel, steer or retry its work. Open the executing instance to control it.

Push/desktop notifications, notification preferences and a general activity feed are deferred. The Inbox is the current attention surface.