Skip to content
How-to Member

Connecting Windsurf to Dailybot

Connecting Windsurf to Dailybot

This article shows you how to connect Windsurf (Codeium’s agentic IDE) to Dailybot so coding agents can emit progress reports to Home. The flow matches other editors: expose Dailybot tools or terminal access to the agent, authenticate once, pin project metadata, then verify in the web app.

Before you begin

  • Install Windsurf and sign in with the workspace your company allows.
  • Confirm your repository includes the Dailybot reporter script or documented CLI command your org uses.
  • Have permission to edit workspace rules or agent instructions so Windsurf knows when to call Dailybot.

Steps

  1. Open your project in Windsurf and locate Rules, Memories, or Workspace instructions — the surface where persistent agent guidance lives.
  2. If your org uses a Dailybot MCP server, add it in Windsurf’s MCP or tool configuration using the host, token, and tool list from your internal runbook (same values Cursor teammates use).
  3. If you do not use MCP, plan to run reports through the built-in terminal Windsurf can invoke when executing tasks.
  4. Open a terminal at the repo root and run dailybot login, or set DAILYBOT_API_KEY in your shell environment or .env file the agent inherits.
  5. Define DAILYBOT_PROJECT_NAME so reports map to the correct Dailybot project when multiple repos exist.
  6. Paste your team’s standard reporter instruction into Windsurf rules — for example requiring bash agent_scripts/dailybot-report.sh "summary" --metadata '{"model":"your-model-id"}' after substantive edits or PR-sized work.
  7. Run the reporter manually once to validate API access and project naming before trusting the agent.
  8. Trigger a small agent task that should conclude with a standup-style summary and approve any terminal command the IDE asks you to run.
  9. Open Dailybot Home and confirm the entry landed within a minute or two (allow for network delay).

What to expect after

Windsurf will only report what its automation is allowed to execute. If commands are blocked by sandbox settings, fall back to running the reporter yourself or loosen terminal permissions per company security policy. For empty feeds, follow My coding agent’s reports aren’t appearing.