Skip to main content
Pulse runs a prompt on a schedule. Use it for repository checks, document digests, report drafts, or read-only briefings. A pulse keeps the mode it was created with. Changing your active space later does not change that scheduled task’s mode.

​
Create a pulse

1

Choose the experience

Select Code, Work, or Chat, then open Pulse.
2

Choose a template or start blank

Templates are filtered for the current mode. They provide a prompt and schedule you can edit.
3

Choose the target and agent

Code requires a workspace. Work and Chat can run without one and can target a collection with shared sources.Choose the provider, model, and supported effort or thinking controls.
4

Set the schedule

Choose hourly, daily, weekdays, or weekly and the relevant time or day.
5

Create and enable

Save the pulse and check its next run time. Scheduled results appear as ordinary runs.

​
Modes and templates

Claude and Codex support Work and Chat pulses. All four providers can run Code pulses. Collection sources are read when each scheduled run starts, so later source updates apply to future executions.

​
Time and availability

Schedules are computed in the backend machine’s local timezone. The stored timezone label is display metadata; it does not provide a separate timezone execution policy. The backend must be running and reachable by its providers. With Desktop, keep Mains running and the Mac awake. For an always-available host, configure Mains Server as a service. If you connect remotely, the schedule runs on that backend, not on the client device.

​
Run settings and approvals

Pulse applies execution settings suited to scheduled work: Claude Auto, Codex Workspace Write, Copilot’s scheduled permission policy, and Cursor Agent mode. Work and Chat policies still apply. A scheduled task can still encounter a provider error, limit, question, or external-tool request. Write prompts that state the desired output and how to handle missing information.

​
Manage pulses

Edit the prompt or schedule, pause a pulse, or delete it when it is no longer needed. Inspect the resulting runs to review output and failures. For keeping issue connections fresh without asking an agent to do work, use Auto Sync. Pulse is not a webhook-triggered workflow.