Heartbeats
Have the agent watch something on the schedule you set. It speaks up when there is something new and stays quiet otherwise — so you don't have to remember to look.
What it is for
Some things are worth knowing but happen rarely: someone in a forum starts complaining about the problem you solve, a page quietly changes. Watching for it is not worth your daily attention, but missing it costs you. A Heartbeat hands that job to the agent: it looks on the rhythm you give it and comes to you only when there is genuinely something new.
Creating one
Say it in a sentence — there is no form to fill in: what to watch, how often, and what is worth telling you about. It then appears under Heartbeats in the sidebar. Changing the rhythm or the criteria is another sentence, and it reads the change back to you to confirm.
Silence is the normal state
Most runs find nothing, and on those it says nothing at all — no unread dot either. That is deliberate: something that reports "no updates" every hour is ignored within two days, and then the one run that mattered is ignored with it. The runs are visible in the conversation if you want them; they just don't interrupt you.
Managing a Heartbeat
Each one lives under Heartbeats in the sidebar. Hover and three controls appear; everything else is changed by saying so in the conversation:
- Pause / resume: a paused Heartbeat does not run and does not spend. Resuming schedules it from now — it does not replay the runs it missed
- Delete: there is a six-second undo. Deleting also drops the record of what it has already seen, so an identical new one will report everything currently there as new
- Change the rhythm, what it watches, or what is worth reporting: say it in its conversation and it reads the change back to you. These are not buttons on purpose — a button cannot express \u201cMonday mornings at nine\u201d, and reading it back is how you catch it mishearing you
- Mute one: a per-Heartbeat switch in notification settings. Muted means \u201ckeep running, just don't push it to me\u201d — not the same as paused
Where notifications go
By default findings land in the conversation. You can also add an incoming webhook from the icon on the Heartbeats row in the sidebar — Slack, Discord, Feishu, WeCom or DingTalk — and new findings are pushed there.
- Each Heartbeat can be muted on its own without affecting the others
- A notification that arrived counts as you having seen it. A Heartbeat only pauses itself when, several times in a row, nothing arrived and you never opened its conversation
How to connect it, what the message looks like, and what to check when nothing arrives: see Heartbeat notifications.
How it spends credits
Every run of a Heartbeat is an ordinary agent run, so it costs what sending a message yourself costs. Worth knowing before you create one:
- A run costs about 20–30 credits: around 20 when it finds nothing, around 30 when it has something to write up. One hourly Heartbeat is roughly 500–700 a day — closer to the top the busier the source
- The runs that find nothing cost too — it still looked and compared, it just had nothing to say
- A tighter rhythm spends faster: every 10 minutes is six times every hour
- You can pause or delete it from the sidebar at any time; once stopped it spends nothing
- You can give it a daily limit: say "spend at most 300 credits a day" in its conversation and it reads the limit back to you. Once reached, it stops for the day and carries on the next
Current limits
- It is in Beta — usable, still being refined, and the behaviour may change
- The clock is minute-grained, so "09:00 sharp" drifts by a few minutes
- Tasks on pages that need a login require your computer awake and the extension enabled; a Heartbeat that only reads public sources does not
Let the agent use your browser → · How credits are charged →