Add an AI coworker in Slack that works in production without your keys
shivsarthak built Doozy, an AI coworker inside Slack that can do work in production without being handed your keys.
Source
shivsarthak on Hacker News · 2026-10-20 · Project link
Written in our own words. Credit to the original author. Link checked 2026-10-24.
What they did
shivsarthak built Doozy, an AI coworker inside Slack that can do work in production without being handed your keys.
Result (as claimed)
Team requests handled from Slack with keys kept private.
Tools they used
Cost: Pricing depends on the tools you pick; check each official pricing page.
Set it up
Map the task
Write the trigger, the inputs, the decisions and the output. Note which steps need a human yes.
Connect the tools
Set up Doozy, Slack with the narrowest permissions that work. Use a test account or sandbox first.
Build the workflow
Create the steps in order. Add an approval step before anything sends, pays or deletes.
Run it on real but low-stakes data
Run a few times, read every output, and fix prompts or rules that misfire.
Schedule and monitor
Turn on the schedule or trigger, and add a daily summary or alert so you notice failures.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Add an AI coworker in Slack that works in production without your keys What the original author did: shivsarthak built Doozy, an AI coworker inside Slack that can do work in production without being handed your keys. Reported result (as claimed by the author): Team requests handled from Slack with keys kept private. Source: https://news.ycombinator.com/item?id=50166515 Tools they used: Doozy, Slack Category: Automation & business Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Add an AI coworker in Slack that works in production without your keys What the original author did: shivsarthak built Doozy, an AI coworker inside Slack that can do work in production without being handed your keys. Reported result (as claimed by the author): Team requests handled from Slack with keys kept private. Source: https://news.ycombinator.com/item?id=50166515 Tools they used: Doozy, Slack Category: Automation & business Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Add an AI coworker in Slack that works in production without your keys What the original author did: shivsarthak built Doozy, an AI coworker inside Slack that can do work in production without being handed your keys. Reported result (as claimed by the author): Team requests handled from Slack with keys kept private. Source: https://news.ycombinator.com/item?id=50166515 Tools they used: Doozy, Slack Category: Automation & business Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Related use cases
Have an AI teammate flag when meeting notes and inventory data disagree
A team's AI agent noticed that meeting notes and the inventory export disagreed on a shipment's landing date and asked the inventory lead about it in Slack.
Use ChatGPT Dots as your orchestrator with Codex as its hands
A product builder sends ChatGPT Dots voice notes, screenshots and ideas from his phone. Dots, connected to GitHub, Slack, email and Figma, raises bugs and manages travel, and hands Codex the sites that block its data-center browser.
Run a personal agent on Railway with Discord channels and an Obsidian memory
A founder runs Hermes on Railway, connected through his own MCP gateway to email, calendar, Slack, X, LinkedIn, GitHub, Obsidian and DNS, with code in a Vercel sandbox. He moved from Telegram to Discord for per-topic channels and has it keep a note on every person he works with in Obsidian.
Deploy an open-source team agent in Slack with your own models
QM, open-sourced by Y Combinator, gives every employee their own agent with memory, files, permissions and a sandbox, and also works in Slack channels: it searches notes, email and docs, triages inboxes, opens PRs and runs scheduled jobs. You deploy it by telling your coding agent to follow the repo guide.