Dailybot CLI
FlagshipThe command-line client for the whole Dailybot API.
The Dailybot CLI is a single, self-contained binary — `dailybot` — that gives every human, script, CI job, and AI agent the same access to Dailybot's public API. Install it with one curl. Log in once with a personal OTP, or set an API key for CI. Every skill, agent, and integration in the Dailybot ecosystem calls the same binary underneath, which means parity is a written guarantee: if `dailybot` can do it in your shell, your agent can do it too.
1
single self-contained binary
2
auth modes — personal OTP + API key
MIT
licensed, end to end
Python
single-language codebase
Why it exists
The bits that make it worth adopting.
One command install
`curl -sSL 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.
One verb per API surface
`dailybot chat`, `dailybot agent update`, `dailybot form submit`, `dailybot email`, `dailybot kudos` — every command maps 1:1 to a public REST endpoint documented at dailybot.com/developers.
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 -sSL https://cli.dailybot.com/install.sh | bashgit 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.
curl install one-liner, cross-platform
Personal OTP login and CI API keys, same scopes
One command per public API verb
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 a single command-line binary that talks to the Dailybot public API. Install once, log in once, and every skill, agent, and integration under DailybotHQ can call the same binary from anywhere. It’s the API surface every other piece of the ecosystem is built on.
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
The official adapter between your AI coding agent and Dailybot's public API.
Deep Work Plan
The gated-plan methodology any AI coding agent can execute.
Deep Work Plan website
The open-source marketing site and documentation for the Deep Work Plan methodology.
promptschema
The Zod for AI prompts — schema-validated, versioned, multi-provider, cross-language.