Turn Slack and call transcripts into Claude Code tasks

The poster wants a persistent Claude agent that watches Slack and call transcripts, spots tasks, and drafts the Claude Code prompts, removing them from the loop.

Done withCLClaudeCCClaude Code

What they did

The post itself is a request, not a finished build: the poster says their company’s Claude enterprise setup already connects to Slack, call recordings/transcripts, a data warehouse, a knowledge base, Google Workspace, and internal tools, and they want a permanent agent to watch Slack and transcripts, identify tasks, draft Claude Code prompts, and let them approve or tweak before running. In comments, the most concrete similar setup described is a small always-on Slack app on a Mac that listens for mentions and alerts, starts Claude Code in headless mode per Slack thread, keeps phase one read-only, and gates write actions, sends, and higher-risk changes behind approval buttons.

How it went

No outcome is reported by the original poster because they are asking for advice. A commenter who built a similar system says it was a "total game changer," but gives no hard metrics; others warn quality can drop without strong approval, deduping, and read-only staging.

Worth knowing

Most actionable catch: start read-only, separate task extraction from execution, and dedupe requests because the same ask may appear in both Slack and call transcripts.

Source: Reddit · Oct 8, 2026