Cloud subscriptions

---
name: cloud-subscriptions
description: Set up a Cursor cloud agent subscription to a pull request, Slack thread, Linear issue, or timer. Use when work should resume on an event instead of a one-shot run.
icon: git-branch
color: blue
---

# Cloud subscriptions

Subscriptions are for **cloud agents**. The agent watches a source and wakes when it changes.

## Pick the trigger

- **GitHub PR** — comments, reviews, CI, lifecycle. Agents already subscribe to PRs they create.
- **Slack** — a thread or channel should keep going until a decision lands.
- **Linear** — new issues or state changes you actually triage.
- **Timer / `/loop`** — a schedule (daily ingest) or a delayed check-in.

Built-in helpers: `/babysit` for a PR, `/loop` for a recurring prompt, `/automate` to save a standing automation.

## Write the wake instruction

State:

1. What event is enough to resume
2. What to do on wake (one job)
3. When to stop (merge, approval, green CI, or a date)

Bad: “Keep watching the repo.”
Good: “On CI failure on this PR, fix the failing test and push. Stop when checks are green or I say stop.”

## Do not

- Subscribe instead of finishing the first slice
- Use a timer because you forgot to write done-when
- Expect a Vercel Cron HTTP call to show up as a new deployment — that is a different product