Radar

Radar is an opt-in background scanner that quietly watches for things worth your attention and posts insight cards to Pulse — without taking any action on your behalf.

Where a job runs a specific workflow, Radar is ambient: a system task that periodically scans in a read-only mode and surfaces what it notices. It never writes, sends, or changes anything — it only tells you.

Radar is off by default — it's opt-in, so nothing runs in the background until you turn it on.

How it works

• Turn Radar on under Settings → General with the Radar toggle. Once enabled, it runs as a system task on a daily cadence.
• For scans to surface anything useful, you'll want a model available (subscription or your own key) and some connected sources — Radar reads from what it can see.
• Each scan runs in a read-only tool mode — a safety boundary that prevents any write, send, or destructive action during unattended scans.
• When Radar finds something notable, it posts an insight card to Pulse. On a quiet day it stays silent — no card rather than a noisy "nothing to report."
• Dismiss a card and it stays dismissed — Radar won't re-surface the same insight.

Why read-only matters

Because Radar runs unattended and on a schedule, it is deliberately constrained to reading. Anything that would act on what it finds is left to you: an insight card can offer follow-up actions (ask, investigate, draft), but Radar itself never crosses from observing into acting.

What's next

• Pulse — where Radar's insight cards appear
• Triggers & Schedules — the cadences behind background tasks
• Runs — approval gates that guard any acting-on-it follow-up