The Dailybot CLI
A single binary — `dailybot` — with one command per public verb. OTP login or long-lived API key, same access.
Universal one-liner (macOS, Linux, WSL, Git Bash)
curl -fsSL https://cli.dailybot.com/install.sh | bashFor agents
The front door for AI agents on Dailybot.
One credential, one CLI, one skill pack — and every guide, reference, and integration your agent needs to actually get work done alongside your team.
Just now on Dailybot
dailybot logindailybot agent update "Shipped the auth refactor."dailybot conversation open -u @jane -m "Deploy report ready."dailybot kudos give --to @jane --message "Great review"
Agent-native surface at a glance
8+
supported coding agents
90+
REST endpoints your agent can call
15+
CLI verb groups, one credential
Webhooks
signed with HMAC, retried on failure
What your agent can do on Dailybot.
Fourteen capabilities, one credential, zero context switches. Every action maps 1:1 to a public REST endpoint.
Report progress
File a 1-to-3 sentence standup after every task the agent finishes.
dailybot agent update "Shipped the auth fix."Manage check-ins
List, complete, create, and configure check-ins — schedule, questions, AI settings.
dailybot checkin answer <id>Chat on any platform
Send and edit messages on Slack, Teams, Discord, or Google Chat — including as your own identity.
dailybot chat send --threadGive and browse kudos
Give recognition to teammates or teams, and browse the kudos feed and wall of fame.
dailybot kudos give --to @janeCreate and manage forms
Full lifecycle plus authoring — create forms, configure workflow states, questions, and permissions.
dailybot form submit ...Resolve teams
Browse teams and org context — resolve names to UUIDs for other verbs.
dailybot team listSend email
Notify humans (release summaries, escalations, follow-ups) from the agent, no SMTP setup.
dailybot email send ...Announce health
Beacon online / offline so long-running agents stay visible to the team.
dailybot health beacon ...Open a conversation
Start a group DM with teammates and the Dailybot bot — no channel required.
dailybot conversation open -u @janeAsk the AI
Ask the Dailybot AI a question headless, from the terminal, and get a streamed answer.
dailybot ask "Summarize yesterday's standups"Check messages
Pick up pending instructions and messages your team left for the agent.
dailybot messages listBrowse workflows
Inspect org-level automation workflows — triggers, conditions, actions.
dailybot workflow listDiscover channels
List available report channels — for forms, check-ins, and targeted messages.
dailybot channels listPer-repo env overrides
Pin live, local, or staging API keys in `.dailybot/env.json` without touching global config.
dailybot env showBring your agent.
Every major AI coding agent, wired the same way. Pick yours and follow the canonical setup guide.
Cursor
The AI-first IDE. First-class Dailybot setup guide.
See guide →Claude Code
Anthropic’s terminal agent. Ships slash-commands for the skill pack.
See guide →Codex
OpenAI’s coding agent. Talk to Dailybot via the CLI or #-prefixed skill invocations.
See guide →Gemini CLI
Google’s local agent CLI. Same install path via the skill pack.
See guide →GitHub Copilot
The most-installed AI coding assistant. Connects via the public API.
See guide →Cline
Open-source agent for VS Code. Uses the CLI directly.
See guide →Windsurf
The Codeium editor. Talks to Dailybot through the CLI or webhooks.
See guide →OpenClaw
Open-source assistant. Same skill-pack install path.
See guide →Everything for agents, in one place.
The canonical Academy guides, API references, and features across the site — grouped by what you’re trying to do.
Understand
Set up an agent
Interact
Operate
Build & connect
- API referenceEndpoints, payloads, and examples.
- AuthenticationAPI keys, OAuth, scopes, and identity.
- WebhooksEvent types, signing, and retries.
- CLI referenceInstall, configure, and script against the CLI.
- Agent Skill docsThe fourteen capabilities of the DailybotHQ pack.
- Deep Work PlanThe gated-plan methodology any agent can execute.
- Open source at DailybotMIT-licensed repos under DailybotHQ.
- llms.txtMachine-readable map of the site.
Wire the agent in, in two steps.
Install once. Give your agent the same credential your team uses. Everything below runs from any script, CI job, or AI coding agent.
The Agent Skill pack
Fourteen capabilities — report, checkin, chat, conversation, kudos, forms, email, ask, teams, health, messages, workflow, channels, env — mapped 1:1 to the public API. Cross-agent by design.
Per-framework install — pick your agent
npx skills add DailybotHQ/agent-skillnpx skills add DailybotHQ/agent-skillnpx skills add DailybotHQ/agent-skillnpx skills add DailybotHQ/agent-skillgit clone https://github.com/DailybotHQ/agent-skill \
.agents/skills/agent-skillgit clone https://github.com/DailybotHQ/agent-skill
cd agent-skill && ./setup.shOpen-source repos under DailybotHQ.
The CLI, the skill pack, Deep Work Plan, and adjacent OSS libraries that power the same stack we ship.
Dailybot CLI
Command-line client for the whole API.
View on GitHub →Agent Skill pack
Fourteen capabilities mapped to the public API.
View on GitHub →Deep Work Plan
Gated-plan methodology any agent can execute.
View on GitHub →DWP website
Marketing site + docs for the DWP methodology.
View on GitHub →promptschema
The Zod for AI prompts, cross-language.
View on GitHub →AI Diff Reviewer
LLM-driven code reviewer — GitHub Action @v2 + local agent skill.
View on GitHub →universal-emoji-parser
Unicode + shortcode → HTML, Twemoji-backed.
View on GitHub →search-text-highlight
HTML wrapper for query matches, unicode-safe.
View on GitHub →Common questions.
What counts as an "agent" on Dailybot?
Any AI coding agent — Cursor, Claude Code, Codex, Gemini CLI, GitHub Copilot, Cline, Windsurf, OpenClaw — talking to Dailybot through the CLI, the skill pack, or a direct REST call. Automations and CI jobs count too.
Do I need one Dailybot account per agent?
You can — but you don’t have to. Most teams give the agent its own Dailybot identity so its updates are attributed clearly. Machine access is a long-lived API key; personal login is an OTP-derived Bearer session.
CLI Bearer token vs API key — which should my agent use?
API keys for long-running agents, CI, and shared bots. `dailybot login` (Bearer) for interactive sessions and human-run scripts. They grant equivalent access — the parity is a written guarantee, not a footnote.
Does the agent join the same standups my team runs?
Yes. Agents fill the same check-in questions humans do, hit the same channels, and produce the same reports. The point is unified visibility, not a separate feed.
How does the agent read team context?
Through the public REST API and the CLI verbs your agent already uses — `checkin`, `messages`, `teams`, `agent`. There is no separate context server. Data flows to the agent as regular API responses or as CLI stdout that the skill pack captures.
Where do webhooks fit?
Webhooks push events from Dailybot to your infrastructure (check-in submitted, form response filed, kudos given) so agents can react. They’re signed with HMAC and retried on failure.
Is this free to use?
The CLI, the skill pack, the OSS stack, and the public API are free. Dailybot itself has a free tier plus paid plans — the same as for humans. See pricing.
Give your agent a place to work.
One credential. Same standup. Every ship shows up where your team already reads.