Skip to content
New Dailybot 3 is live. Read the launch
Troubleshooting Web Admin developer

Agent setup failed (Cursor, Claude Code, Copilot, Windsurf)

Agent setup failed (Cursor, Claude Code, Copilot, Windsurf)

When you connect an AI coding agent (Cursor, Claude Code, Copilot, Windsurf, custom) to Dailybot, three things must line up:

  1. The agent identity is registered to the right Dailybot org.
  2. The token the agent uses is valid and not expired.
  3. The agent is emitting events that Dailybot understands.

If any of those fails, the dashboard shows the agent as offline or never reported. This page walks the diagnostic ladder.

Quick check (2 minutes)

  1. Open Home -> Agent dashboard in the Dailybot web app.
  2. Find the agent. Status options:
Status Meaning
Online Setup is fine – the issue is elsewhere.
Offline (recently) Connected before, not in the last heartbeat window. See Heartbeat stopped.
Never reported Setup never completed end-to-end. Continue with this page.
Mass deactivation Many agents went offline at once – see Mass deactivation.

If the agent is not in the list at all, registration did not even create the record.

Step 1: confirm the right org

A very common failure: you registered the agent to your personal / test org while you expected it in the company org.

  • In Dailybot, click the org name top-left – this is your current org.
  • Open the agent’s local config (Cursor settings, Claude Code settings, etc.).
  • Look for the API key or token – compare it with the token you generated.
  • Each token is bound to one org. If you set up the agent with a token from org A, it will not appear in org B’s dashboard.

Re-generate a token in the correct org and re-paste it in the agent. See the platform-specific guides:

Step 2: validate the token

Symptoms of an invalid token:

  • The agent’s logs show 401 or 403 when calling Dailybot.
  • The dashboard says Never reported.
  • “Invalid agent token” or similar in the chat.

Fixes:

  1. In Dailybot, open Settings -> Developer / Agents -> Tokens.
  2. Confirm the token still exists – tokens may have been revoked by an admin.
  3. If expired or revoked, create a new one and update the agent config.
  4. Restart the agent so it picks up the new token.

If your token has never worked, copy it again carefully – trailing spaces and missed characters are the #1 cause of “invalid token”.

Step 3: confirm heartbeats are reaching Dailybot

If the token is valid and the agent ran, Dailybot expects a periodic heartbeat. If none arrives:

  • Network – agent is on a network that blocks outbound HTTPS to *.dailybot.com.
  • Firewall / VPN – a corporate firewall is dropping the requests. Allowlist the Dailybot domains.
  • Agent crashed silently – check the agent’s local logs for unhandled errors.
  • Wrong endpoint – a stale config pointing to a deprecated URL.

For more, see Heartbeat stopped.

Step 4: events show up but nothing happens

Sometimes the agent is registered and online, but you do not see the expected report or summary.

  • Open Home -> Agent reports – did the report actually arrive?
  • If yes but the format looks wrong, the agent is sending events but not the reportable ones. Check the platform guide for required event shapes.
  • If no, see Agent reports missing and Inbox delivery failure.

Setting up your first agent end-to-end

If you have never connected an agent before, follow First agent setup. Doing that walkthrough once usually surfaces whichever step is breaking for you.

When to escalate to support

Collect:

  • Org name and your email.
  • Which agent (Cursor / Claude Code / Copilot / Windsurf / custom).
  • Token ID (the prefix, not the secret).
  • Last successful heartbeat if any.
  • A snippet of the agent’s local logs showing the failure.
  • Network notes (corporate VPN? proxy? known firewall?).

Then contact Dailybot support from Help / Contact in the product or on the website.