Skip to content
How-to Member

Connecting Claude Code to Dailybot

Connecting Claude Code to Dailybot

This article shows you how to connect Claude Code to Dailybot so agent progress reports reach your Home feed.

Before you begin

  • Claude Code must run in an environment where you can install the Dailybot CLI (or use an MCP server that wraps the same API).
  • You need a Dailybot API key or the ability to run dailybot login in that environment.
  • Your repo should include or allow adding the small reporter script and env files your team standardizes on (often agent_scripts/dailybot-report.sh and .dailybot.env).

Steps

  1. Install the Dailybot CLI on the same machine or container where Claude Code runs.
  2. Open a terminal in your project root and run dailybot login, or export DAILYBOT_API_KEY with a key from the Dailybot dashboard under API or developer settings.
  3. Add a project name Dailybot can use for grouping: set DAILYBOT_PROJECT_NAME in .dailybot.env (team-shared) or .env, or match your devcontainer.json name if your template uses that fallback.
  4. Wire Claude Code to call the reporter when meaningful work finishes — for example a hook or skill that runs bash agent_scripts/dailybot-report.sh "short standup-style message" --metadata '{"model":"your-model-id"}' (adjust path and flags to your repo).
  5. Send a test report from the terminal with a clear message (for example “Test connection from Claude Code setup”).
  6. Open Dailybot in the browser, go to Home, and confirm the test report appears within a minute or two.
  7. If nothing appears, check the terminal for CLI auth warnings, confirm DAILYBOT_PROJECT_NAME is set, and see My coding agent’s reports aren’t appearing.

What to expect after

Successful runs create entries in Home tied to your user, project name, and any metadata you pass (repo, branch, plan name, model). Claude Code does not need to stay open for old reports to remain visible. Ongoing reporting is driven by your hooks or manual calls — Dailybot does not poll your filesystem.