Agent reports: how they work
Agent reports are structured updates from coding agents that log activity in repos, tasks, or CI and send summaries into Dailybot.
What a report contains
A typical report includes:
- A short activity summary — what the agent worked on or observed in the reporting window.
- Progress updates — milestones, PRs, tickets, or steps your integration maps into text.
- References — links or identifiers to commits, branches, builds, or external systems when your setup provides them.
Fields depend on your integration and payload. The goal is a concise status without opening every tool.
How reports are generated
Agents push data via the Dailybot CLI, API, or configured SDK path. Dailybot ingests the payload, validates it, stores it, and displays it on the feed, dashboard, and optional chat.
If the agent stops calling the API or auth breaks, reports stop. Use the troubleshooting article for missing reports when updates do not appear.
How reports connect to standups
Dailybot can map agent output into check-ins. With auto standup agents enabled, report data may pre-fill or suggest answers (for example “what did you ship”) for people to confirm or edit.
Admins turn that link on and pick the check-in template. Members still submit the check-in.
Where reports appear
- Home feed — recent agent reports mixed with other team signals you configured.
- Agent dashboard — managers and admins see history, filters, and health next to the same report stream.
- Chat channels — optional posting to Slack, Teams, Discord, or Google Chat when your org routes summaries to a channel for visibility.