Troubleshooting

It was cancelled — the Stop button ends a generation in progress. Just send your prompt again to retry.

Your agent keeps working even if you navigate away. Reopen the conversation and it reconnects — you don’t lose the result.

Credits cover more than the reply — memory updates, tool calls and skills all draw from your balance. If you have a Heartbeat, it spends while you are away: every run counts, including the ones that find nothing. Open Billing → Usage Detail to see exactly what each credit went to. See Billing & Credits and Heartbeats.

Check it isn’t switched off in the strip by the prompt box, and remember the difference between uploaded and reused references. See Reference images.

The selected agent sticks across turns — check the agent badge by the prompt box, or type @ to switch. The @ mention is never sent as part of your prompt.

A saved preference may be steering it. Open Memory to see what your agent remembers, and remove anything that no longer fits. See Memory.

It may have a condition — for example, showing only when you’ve attached an image — or the built-in prompts are toggled off. See Prompts.

Resend it from the sign-in screen or the “check your email” page. Give it a minute, and check your spam folder.

The image may be smaller than the minimum size (128px by default), or Buddy is disabled for that site — both are in the extension’s Settings. See Buddy extension.

The usual cause is that the group bot requires a custom keyword and the message does not contain it — the receiver then rejects the message without raising an error. Set the keyword to Agentic Hat: every notification is signed with it. Open the icon at the right of "My Heartbeats" in the sidebar; a rejected destination shows the reason on its row. Press Test once and check the message really arrived. A destination that keeps failing is switched off automatically — add it again to restore it. See Heartbeat notifications.

There are four cases, and the sidebar shows it as paused. One: it reported several times and nobody looked — reading its conversation counts, and so does a notification that reached your group; with neither, it stops itself rather than keep spending. Two: it hit the daily limit you gave it — this is not a pause, and it carries on the next day. Three: credits ran out — when the wallet it is billed to (yours or your organization's) has no credits left, it stops before running and tells you; after you top up it resumes by itself at its next scheduled time, nothing to press. Four: several runs failed in a row, for example because the browser it needs stayed offline. Cases one and four need you to resume it from the sidebar.

The extension cannot run on a phone; the work is done by the browser on your computer. That needs Buddy installed there, the Agentic Hat chat page open, and the computer awake — all three. See Drive your desktop browser from your phone.