Skip to content
All posts

Keep one Live Activity current

Use a stable activity ID to update one useful result as your work changes.

A background workflow can produce plenty of updates and still leave you with the same question: what needs me now?

I 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.

Start with one subject

Choose 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.

That 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.

Report the evidence you have

If 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.

For a funnel, compare stages from the same cohort and time window. The gallery's activation funnel uses sample values of 100%, 72%, 58%, and 41%. Those are illustrative measurements, not customer results.

After installing the Swift CLI, download funnel.json and send the example:

agentalerts send --file funnel.json --activity-id funnel

When your real measurements change, update the content and reuse the same activity ID. Keep missing data unknown instead of turning it into zero.

Decide what deserves a notification

A 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.

Useful 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.

Your 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.

Check the first result

Use a non-sensitive test, read the returned status, and look at your iPhone. A service accepting the request does not establish visible delivery.

The 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.

The aim is a useful glance: what changed, why it matters, and what to do next.

Send your first update or explore the available examples.