My coding agent’s reports aren’t appearing
Your IDE or CLI agent is running, but summaries, PR activity, or Dailybot Home updates never show up. Usually the agent is not connected to Dailybot, the auth token expired, or network calls from your machine are blocked.
Quick check
- Connection status — In the Dailybot web app, open agent or Home settings and verify the agent shows Connected (wording may vary).
- CLI or plugin login — Re-run the Dailybot login or API key step in Cursor, Claude Code, or your supported tool.
- Token expiry — If you changed passwords or revoked OAuth, reconnect the integration.
- Network / VPN — Corporate proxies sometimes block agent heartbeat URLs; try off VPN or allowlist Dailybot endpoints per your IT policy.
- Correct organization — Ensure the CLI points at the same Dailybot org where you expect reports.
Common causes and fixes
Agent not connected to Dailybot
First-time setup is easy to skip. Complete the flow in Set up your first agent and the guide for your editor:
Until the plugin registers, Dailybot has nothing to ingest for reports.
Authentication expired or revoked
Long-lived tokens can expire after security resets. Symptoms: agent worked last week and stopped with no config change. Open Dailybot settings, disconnect the coding agent if needed, and sign in again from the IDE extension. Generate a new API key only if your docs say to — some flows use OAuth instead.
Network or firewall blocking delivery
Agents send HTTPS events from your machine to Dailybot. Strict TLS inspection or offline mode blocks them silently. Test from another network, check corporate SSL inspection exceptions, or ask IT to verify outbound HTTPS to Dailybot domains.
Reports go to a view you are not watching
Some setups post to Agent dashboard or Home feeds rather than email. Open Agent reports in Home and the Agent dashboard to confirm whether data arrived in a different surface.
If none of this worked
Include in your support message:
- Editor and extension version
- OS and whether VPN is required
- Last time a report succeeded
- Any error text from the CLI or IDE output (redact secrets)
We can trace delivery on our side with timestamps you provide.