Connecting your first coding agent
Dailybot tracks coding agent activity — progress reports, commits, and time spent — and surfaces it in the Home feed. This article walks through connecting any supported coding agent.
Before you begin
- You need a Dailybot account and access to the web dashboard.
- You need permission to install the Dailybot CLI, an extension, or an MCP integration where the agent runs.
- If you use key-based auth, create or copy an API key from the dashboard before you start — do not commit keys into the repo.
- Confirm with your org admin if connections are limited to certain projects or environments.
Steps
- Sign in at app.dailybot.com with the account tied to your organization.
- Open Settings and go to Agent Connections or the equivalent coding-agent section (exact names can vary by plan).
- Choose your agent type. For step-by-step install and auth, use Connecting Claude Code to Dailybot or Connecting Cursor to Dailybot.
- Install the Dailybot CLI, extension, or MCP package in that environment, then authenticate with
dailybot loginorDAILYBOT_API_KEYas the guide describes. - Set
DAILYBOT_PROJECT_NAMEin.envor.dailybot.env(or your team’s standard) so reports map to the right project or repo. - Run one test progress report using the reporter command your template documents.
- Open Home in Dailybot and confirm the test shows the expected project name and timestamp.
What to expect after
Connected agents send data when your workflow invokes the reporter or related integrations. Home aggregates that stream so the team can scan activity without opening each IDE. How much commit or time detail you see depends on what your setup forwards — Dailybot displays what it receives. Who can read each item follows your organization’s Home visibility settings.