Unattended agent work?
++ Schedule fresh Pi sessions with fixed models and hard timeouts, then inspect run duration, tokens, and + estimated cost from the workspace Automations view. +
+ Explore automations → +
+
+ Durable agent work
+Schedule Pi sessions. Keep control of every run.
+Create workspace automations with explicit models and deadlines, then inspect which jobs ran, how long they took, and how many tokens and estimated dollars they consumed.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Create, test, then enable
+Select a machine, project, and workspace, then open Automations in the workspace panel. New definitions are saved disabled. Use Run now to test the exact revision before enabling its schedule.
+Editing a job creates a new revision, pauses it, and requires another completed manual test. Each run gets a fresh, independent Pi session.
+Machine-owned, federation-aware
+Automations belong to the machine that owns the selected workspace. For a federated machine, the controlling gateway forwards automation requests while the remote pi-web-sessiond stores definitions and history, resolves its own models and workspace, and runs the schedule locally.
The browser and controlling gateway may disconnect or restart without stopping the remote schedule. The unversioned automations capability is the stable baseline federation contract; future optional operations will use separate feature capabilities. Definitions are not replicated and do not fail over automatically. To move one, recreate it against a destination workspace so that machine can validate its model and settings.
Manual and scheduled triggers
+-
+
- Manual: run only on demand. +
- One shot: run once at a future timestamp. +
- Interval: use a fixed cadence of at least one minute. +
- Cron: use a six-field expression and an explicit IANA timezone. +
The same automation never overlaps itself. Colliding scheduled occurrences are recorded as skipped instead of starting another session.
+Visible model and thinking settings
+Every automation card shows its model, provider, thinking policy, and timeout. Fixed models are validated again at dispatch and never silently replaced. Historical runs preserve the actual model and thinking level that were used.
+Hard deadlines and durable cancellation
+The default execution timeout is 60 minutes and can be set from one minute through 24 hours. PI WEB records cancellation intent before aborting the Pi session. If a soft abort does not settle within 15 seconds, it force-closes the runtime.
+Runs become unknown when PI WEB cannot prove termination. Cancellation cannot undo external effects that already completed.
Run inbox and visual analytics
+The workspace view includes a run timeline, median and p95 duration, outcomes, root-session tokens, estimated spend, per-automation usage totals, and links to resulting sessions.
+Costs are model-pricing estimates unless a provider reports an authoritative charge. Unknown and partial usage stays visibly unknown rather than becoming zero. Current totals cover the fresh root session and do not silently include untracked subagents or paid external tools.
+Daemon-owned persistence
+Definitions, revisions, occurrences, attempts, cancellation, and terminal usage live in automations.sqlite under $PI_WEB_DATA_DIR. The daemon acquires an exclusive runtime-owner record before listening or recovering work, so a second live daemon using the same database refuses to start. Browser and web/API restarts reconstruct state from the long-lived session daemon.
After an unexpected daemon restart, queued runs remain eligible, while ambiguous starting or running attempts become unknown and are never blindly repeated.
+The unreleased schedule-plugin prototype's .pi-web/scheduled-sessions.json format is not imported because it lacks the revision, attempt, cancellation, and accounting records required by this runtime. Development-branch prototype definitions must be recreated.
Know the boundary
+A fresh session isolates conversational context, not the host. Automations run with the target machine's Pi configuration and OS-user permissions. PI WEB revalidates the registered project and workspace before dispatch, but prompts and tools can still exercise the permissions granted to Pi.
+ +