Run scheduled agent jobs while my computer is off

Job: design and run a few cloud agent jobs that work on a schedule, even when my laptop is closed.

Shared on X by Aaron Makelky (@theaaron), 2026-10-16: https://x.com/theaaron/status/2111239930915832098. Full how-to and copyable prompt on his blog: https://aaronmakelky.com/blog/how-to-use-cursor-automations. He runs these as Cursor Automations (cloud agents at cursor.com/automations); the same jobs work as Grok Bot routines or GBrain scheduled work.

What you need: a Cursor plan with cloud agents (or Grok Bot / GBrain), and the tools you already use connected (email, calendar, meeting notes, CRM, GitHub).

Five job shapes from his post:
1. Inbox triage: once a day, read one mailbox and file only the threads a person must see (who, what they asked, date). Never reply, forward or draft as me. If nothing qualifies, stop.
2. Chief-of-staff repo: when an email, form or webhook arrives, write one markdown note (source, owner, next action) into a private operations repo.
3. Meeting notes: once a day, pull new transcripts from my meeting tools, skip duplicates, and list decisions and follow-ups I own.
4. Lead intake: when a new business conversation shows up, file a lead note with public context you can verify and route it to the pipeline owner. Don't email the lead.
5. Morning briefing: on weekday mornings, build one short brief from today's calendar, inbox items that need a decision and my open loops. Label any source you couldn't reach; never fill a gap with a guess.

Prompt (adapted from his blog): "You design scheduled cloud agents for me. Before proposing anything, ask me only what you can't infer: which tools are connected, the check I do by hand more than twice a week, where results should land, how I want a morning brief delivered, and what must stay in my hands (sending, spending, booking, posting, deleting). Then give me three automations, each with a name, a trigger (cron with time zone, or the event), a destination, and the exact prompt."

Rules: each job does one thing and stays quiet when nothing changed. Nothing sends, books, spends, posts or deletes without my OK. Review the first week of results before adding more jobs.

Other cloud agents that run on a schedule (checked in their docs 2026-10-18): Lindy routines run on a schedule (daily, weekly or monthly) or on an event like an email arriving, and deliver to Lindy chat, a text or Slack (docs.lindy.ai/teammate/routines). Manus Automations run on a schedule you set (with a time zone) or when an event happens in a connected app such as GitHub, Shopify or email (manus.im/docs/automations). Turn off any skip-confirmation setting until you've checked the first week of runs.