Automations that run without a model (deterministic run mode)
Add a deterministic run mode for automations: a run that executes tool calls with loops, conditions, durable state and computed arguments, and completes without starting a model session. The model becomes optional per run.
Requested capabilities, in priority order: a no-model run mode that records Completed; for-each over an array from a gathered result with a maximum item count; if/else on values from earlier steps; computed arguments (string templates over step results, size-capped and escaped); durable key-value state per automation; a higher write-step cap for no-model runs under a per-run write budget and the destructive-action acknowledgment; a clean "nothing to do" exit that records Completed and sends no failure email; an optional step that starts the model only when a condition is true; or, as an alternative to several of these, a sandboxed code step.
Safety expectations: dry-run blocks writes and logs would-be calls, every deterministic write appears in the run record with its resolved arguments, and fixtures and replay work for these runs. Use case: rule-based monitoring and sync automations (for example UniFi monitoring into Halo tickets every 10 minutes) where the model adds cost and no judgment. Requested on support ticket #330.
Log in to comment and vote
No comments yet
Be the first to share your thoughts.