Skip to content
How-to Member

Connecting Copilot to Dailybot

Connecting Copilot to Dailybot

This article shows you how to connect GitHub Copilot (in VS Code, Visual Studio, JetBrains, or other supported hosts) to Dailybot so progress reports from AI-assisted workflows can reach Home, using the same pattern as Cursor or Claude Code: install or enable the integration surface, authenticate the Dailybot CLI or API, configure the repository, then verify delivery.

Before you begin

  • Install GitHub Copilot in your editor and sign in with the account your company approved.
  • Install the Dailybot CLI locally or ensure your repo documents how agents invoke it (dailybot login or DAILYBOT_API_KEY).
  • Open the project folder that contains agent_scripts/dailybot-report.sh or your team’s equivalent reporter so paths resolve correctly.

Steps

  1. Open your editor’s Extensions or Plugins marketplace and confirm Copilot is enabled for this workspace.
  2. Add Dailybot connectivity the way your org standardized it — for example install a Dailybot extension if provided, wire a Dailybot MCP server in the editor’s MCP settings, or rely on the integrated terminal only (no extension) if that is your policy.
  3. Restart the editor if prompted so MCP or shell integrations load.
  4. Open the integrated terminal at the repository root and run dailybot login, or export DAILYBOT_API_KEY in your shell profile or project .env file.
  5. Set DAILYBOT_PROJECT_NAME in .env or .dailybot.env so reports attribute to the correct Dailybot project.
  6. In Copilot custom instructions, workspace rules, or .github/copilot-instructions.md, add a line that tells the agent to run the reporter after meaningful work — mirror the snippet your repo uses for Cursor (for example bash agent_scripts/dailybot-report.sh "message" --metadata '{"model":"your-model-id"}').
  7. Run the reporter once manually from the integrated terminal to confirm credentials and project name work outside Copilot.
  8. Ask Copilot to perform a small tracked task and ensure it executes the reporter command (you may need to approve the shell command depending on editor safety settings).
  9. Open Home in the Dailybot web app and confirm the test entry appears with the right timestamp and project.

What to expect after

Copilot does not replace Dailybot authentication — it only runs commands you authorize. Successful setup means every approved reporter invocation shows up in Home alongside other agents. If nothing appears, compare your setup with Connecting Cursor to Dailybot and use My coding agent’s reports aren’t appearing.