{"id":109411,"title":"Dailybot CLI: Your AI agents now report to the team","tagline":"An open-source CLI and skill that turns private agent work into team updates, approvals, and workflows in chat","body":"Hey everyone! we’re Mauricio and Sergio, co-founders of Dailybot (YC S21).\n\n**What Dailybot is**: a place for team updates, check-ins, and coordination inside Slack, Microsoft Teams, Discord, and Google Chat. For people and AI agents.\n\n**TL;DR**: we built an open-source CLI so people, scripts, and AI agents can drive Dailybot from the terminal. Updates, check-ins, chat messages, forms, and more land where the team already works: Slack, Microsoft Teams, Discord, or Google Chat. **Ask:** ask your agent to try our skill ([**www.dailybot.com/skill.md**](http://www.dailybot.com/skill.md)), run one workflow that matches how your team actually works, and tell us which one helped you move forward today.\n\nDailybot skill: [**https://www.dailybot.com/skills/agent-skill/#install**](https://www.dailybot.com/skills/agent-skill/#install)\n\n**Demo**\n\n[**Dailybot CLI + Agent Skill: Connect your AI coding agent to your team**](https://www.youtube.com/watch?v=rwopfsPzgSQ)\n\n\\\n**The problem**\n\nTeams are getting real work done with coding agents and scripts. A lot of that work still finishes in a private session. The rest of the team only hears about it if someone rewrites it into Slack or a standup.\n\nSo you get the usual mess: invisible agent work, stale status during a release, approvals bouncing between tools, and check-ins that someone rebuilds by hand for every new project.\n\n**What we shipped**\n\nDailybot CLI. Same Dailybot account and team feed you already use, now from the command line. A few workflows we’re highlighting:\n\n1. Agent update to team chat — done / next / blockers show up in the feed, without a human rewrite\n2. One status message that stays current — one release/status message you keep updating, instead of a pile of outdated posts\n3. Simple approvals in chat — approve/reject in Slack or Teams; your system gets the result and work continues\n\nThere’s more under the hood (forms, check-in creation, agent inbox, activity into reports, kudos, teams, workflows). We’re leading with the ones that produce a visible team result fast.\n\n**Installing the CLI**\n\nEasiest path: pass the skill to your agent and ask it in plain language, e.g. “post a team update that we finished the CLI install path” – [**https://www.dailybot.com/skill.md**](https://www.dailybot.com/skill.md)\n\n**How we got here**\n\nWe’ve been building Dailybot for hybrid teams for a while: async check-ins, reports, and coordination inside chat. As our own team (and customers) started running agents all day, the gap got obvious: agents ship work, humans still retype the update.\n\nThe CLI is our answer to that gap. A bridge into the place the team already coordinates.\n\n**Our ask**\n\n1. Install and try one workflow: [**https://www.dailybot.com/skills/agent-skill/#install**](https://www.dailybot.com/skills/agent-skill/#install)\n2. Reply with the workflow you’d want documented/explored next\n3. If useful, intros to eng teams already running agents in production (contact our founders)\n\nThanks,\\\nMauricio \u0026amp; Sergio","slug":"SSh-dailybot-cli-your-ai-agents-now-report-to-the-team","created_at":"2026-08-05T16:22:36.120Z","updated_at":"2026-09-18T00:35:35.537Z","total_vote_count":22,"url":"https://www.ycombinator.com/launches/SSh-dailybot-cli-your-ai-agents-now-report-to-the-team","share_image_url":"//bookface-static.ycombinator.com/assets/ycdc/yc-og-image-c440a0ad1dacfb86eeeb343717479cc54d256614449b4ef719977a0a451f8bc8.png","company":{"id":24153,"name":"Dailybot","slug":"dailybot","url":"https://www.dailybot.com/","logo":"https://bookface-images.s3.amazonaws.com/small_logos/f727e5abc1675504008ed497195c21034c360412.png","batch":"Summer 2021","industry":"B2B","tags":["Artificial Intelligence","Developer Tools","SaaS","Collaboration","AI Assistant"],"search_path":"https://bookface.ycombinator.com/company/24153"}}