Dailybot CLI
FlagshipThe full platform CLI for Dailybot — current release 3.7.3 on PyPI.
The Dailybot CLI is the full platform CLI — current release [3.7.3 on PyPI](https://pypi.org/project/dailybot-cli/). One `dailybot` binary covers the verb families your agents and CI already need: chat, forms, hooks, env, check-ins, kudos, conversations, and ask. Install with curl, `pip install dailybot-cli`, or Homebrew. Log in once with a personal OTP, or set an API key for CI.
3.7.3
current release on PyPI
7
install channels — curl, pip, brew, and more
2
auth modes — personal OTP + API key
MIT
licensed, end to end
Why it exists
The bits that make it worth adopting.
One command install
`curl -fsSL https://cli.dailybot.com/install.sh | bash` — installer detects your platform, drops the binary in `~/.dailybot/bin/`, and appends the right shell RC. Works on macOS, Linux, and WSL out of the box. No admin, no build step.
Two auth modes, one behavior
`dailybot login` for humans (short-lived OTP-derived Bearer session) or `DAILYBOT_API_KEY=…` for CI and long-lived agents. Same scopes on both paths. Parity is written into the contract — no surprises when moving from local to CI.
Full platform verb families
`chat`, `form`, `hook`, `env`, `agent update`, `checkin`, `kudos`, `conversation`, `ask` — every command maps 1:1 to a public REST endpoint documented at dailybot.com/developers. Current release: 3.7.3.
Machine-friendly output
Every command supports `--json` for machine parsing and a human-friendly default. Exit codes are meaningful. `dailybot --version` is a plain semver string. Great scripting citizen.
Cross-platform, dependency-light
Python stdlib only for the runtime path. No Docker image required. No global Node install. Binary ships with everything it needs to talk to Dailybot from any shell.
MIT + fully forkable
Fork it, self-host it, wrap it, ship it — the whole CLI is MIT-licensed and lives in the open. Nothing about your access to the API is locked to Dailybot's binary.
Install
Get started in seconds.
Pick the channel that matches your stack. Every path lands you in the same working state.
curl -fsSL https://cli.dailybot.com/install.sh | bashpip install dailybot-clibrew install dailybothq/tap/dailybotgit clone https://github.com/DailybotHQ/cli
cd cli && ./setup.shexport DAILYBOT_API_KEY=dbk_...
dailybot agent update "Deploy succeeded"In practice
What teams actually do with it.
01
AI coding agents that report to the team
Every major AI coding agent — Claude Code, Cursor, Codex, Gemini, Copilot — installs the Agent Skill and calls the `dailybot` binary underneath. One CLI, every agent, same team feed.
02
CI/CD pipelines that speak the team's language
Set `DAILYBOT_API_KEY` in CI, and every deploy, release, or nightly job can post to the standup, submit a release form, or kudos a code owner. No custom scripts per pipeline — one CLI, one API.
03
Personal scripts and shortcuts
Every developer's `~/bin` accumulates little scripts. Wrapping them around `dailybot` means the same one-liner works from your terminal, from a Makefile, or from an agent session.
04
Bots and integrations without a full SDK
Building a small integration? Skip the SDK. `dailybot` is a stable API surface with human output for exploration and JSON output for scripting.
At a glance
The short list.
Full platform CLI — current release 3.7.3
Personal OTP login and CI API keys, same scopes
Chat, forms, hooks, env, check-ins, kudos, conversations, ask AI
Skills and agents all call this same binary underneath
FAQ
The questions we hear the most.
What does the CLI power?
Every skill, agent, and integration Dailybot ships. The Agent Skill, DWP, per-language SDKs, and everyone's personal scripts all call the same `dailybot` binary underneath. That's what makes parity possible: one API surface, one binary, one auth path.
How is auth handled in CI?
Set `DAILYBOT_API_KEY` as a secret in your CI environment. The CLI reads it automatically. Scopes are identical to a personal `dailybot login` session — no scoped-down surprises when your agent runs in CI.
Can I use it from a language other than Python?
Yes. The binary is language-agnostic — call it from Bash, Node, Ruby, Go, anything that can invoke a subprocess. `--json` output plays nicely with `jq`, `zx`, or `subprocess.check_output`.
Is it really a single binary?
The installer drops one binary at `~/.dailybot/bin/dailybot` plus one PATH edit in your shell RC. That's it. Uninstall by deleting the folder.
What it is
dailybot is the full platform CLI for Dailybot — current release 3.7.3. Report progress, send messages, create forms and check-ins, manage hooks and per-repo env overrides, give kudos, open group conversations, ask the AI assistant — install once (curl, pip, or brew), log in once, and every skill, agent, and integration calls the same binary.
Why teams use it
Because “how does my automation talk to Dailybot?” should have one answer, not four. Whether the caller is a human at their terminal, a nightly CI job, an AI coding agent, or a webhook script, the CLI is the same. That parity — same commands, same auth, same output — is what makes it a reliable foundation.
How it fits the ecosystem
Every open-source project under DailybotHQ that touches the API funnels through this CLI. The Agent Skill is a wrapper. The Deep Work Plan Dailybot addon is a wrapper. The team’s private automations are wrappers. Which means: if the CLI works, the ecosystem works.
Ready to try it?
Open source, MIT-licensed, and shipping in production at Dailybot every day. Fork it, wire it in, contribute back.
Other Dailybot open source
Dailybot Agent Skill
Fourteen capabilities that turn your AI coding agent into a real Dailybot teammate.
Deep Work Plan
The gated-plan methodology any AI coding agent can execute.
Deep Work Plan website
The open-source documentation hub for the Deep Work Plan methodology.
promptschema
The Zod for AI prompts — schema-validated, versioned, multi-provider, cross-language.