{"document":{"id":"agent-alerts-blog-keep-one-live-activity-current","kind":"blog","slug":"keep-one-live-activity-current","title":"Keep one Live Activity current","description":"Use a stable activity ID to update one useful result as your work changes.","keywords":["Agent Alerts","workflow","stable activity ID","progress","Live Activity"],"publishedAt":"2026-11-10","updatedAt":"2026-11-10","content":"# Keep one Live Activity current\n\nUse a stable activity ID to update one useful result as your work changes.\n\nA background workflow can produce plenty of updates and still leave you with the same question: what needs me now?\n\nI built Agent Alerts to put a short, useful result on the iPhone. One of its most useful habits is simple: keep the same Live Activity current as the work changes.\n\n## Start with one subject\n\nChoose a subject you will want to glance at again: a release, a research task, or the same onboarding cohort. Give it a stable activity ID.\n\nThat ID is the thread connecting the updates. The next send should replace the useful state of that subject, rather than starting another surface with another name.\n\n## Report the evidence you have\n\nIf you know that 18 of 25 steps are finished, a progress ring is useful. If the work is open-ended, a short status and next step can be more honest than a percentage.\n\nFor a funnel, compare stages from the same cohort and time window. The [gallery's activation funnel](/agent-alerts#workflow) uses sample values of 100%, 72%, 58%, and 41%. Those are illustrative measurements, not customer results.\n\nAfter [installing the Swift CLI](/agent-alerts/docs/swift-cli), download [funnel.json](/agent-alerts/examples/funnel.json) and send the example:\n\n```bash\nagentalerts send --file funnel.json --activity-id funnel\n```\n\nWhen your real measurements change, update the content and reuse the same activity ID. Keep missing data unknown instead of turning it into zero.\n\n## Decide what deserves a notification\n\nA current Live Activity and an interruption do different jobs. Agree with your agent on what can sit quietly in the activity and what needs a notification.\n\nUseful triggers might be a result ready for review or a blocker that needs a decision. An internal step finishing is not automatically a reason to interrupt you. An agent turn ending also does not prove the whole task is finished.\n\nYour AI client still owns the checks, source access, and recurring schedule. Agent Alerts shows the result the workflow sends. Connecting it does not start monitoring by itself.\n\n## Check the first result\n\nUse a non-sensitive test, read the returned status, and look at your iPhone. A service accepting the request does not establish visible delivery.\n\nThe same care applies to the content. Keep sensitive details in an authenticated destination and use neutral Lock Screen copy when that is enough to help you decide what to open.\n\nThe aim is a useful glance: what changed, why it matters, and what to do next.\n\n[Send your first update](/agent-alerts/docs) or [explore the available examples](/agent-alerts/docs/live-activity-examples).\n","path":"blog/keep-one-live-activity-current","url":"https://www.andreas.ink/agent-alerts/blog/keep-one-live-activity-current","markdownUrl":"https://www.andreas.ink/api/agent-alerts/content?path=blog%2Fkeep-one-live-activity-current&format=markdown"}}