Anthropic's new Claude Tag is an always-on AI teammate that lives in Slack — but it's locked to Enterprise. This is the build-it-yourself blueprint: 4 pillars, real code, and a no-code path.

Get the free Build-Your-Own AI Teammate blueprint

Anthropic just launched Claude Tag: an always-on Claude that lives in your Slack, breaks tasks into stages, learns your channel, works asynchronously, and (in 'ambient mode') even speaks up on its own. 65% of Anthropic's product team's code now goes through their internal version of it. The catch: it's in beta for Claude Enterprise and Team customers only, and runs on Opus 4.8. So this field guide shows you how to build the SAME thing yourself with tools anyone can get — matching the video beat for beat. THE TARGET — the 4 behaviors that make it a teammate, not a chatbot (multiplayer shared identity, learns over time, takes initiative, works async). PILLAR 1 · THE CORE LOOP — a Slack app using Slack's official Bolt toolkit (@slack/bolt for JS, slack_bolt for Python): subscribe to the app_mention event, grant just two scopes (app_mentions:read + chat:write), pass the text to Claude via the Anthropic SDK on model claude-opus-4-8, and reply in-thread with thread_ts; Socket Mode for local dev, the Events API for production. PILLAR 2 · TOOLS (MCP) — how the Model Context Protocol lets Claude actually use your tools and data, plus the honest catch most guides skip: Slack's official MCP server is real but gated to published/internal apps, so wire MCP servers for the tools you control and read Slack messages through its normal Web API. PILLAR 3 · MEMORY — three ways to make it 'learn over time', simplest first: replay recent channel history as context (free), a vector database for long-term recall (RAG), or Claude's own memory tool. PILLAR 4 · AMBIENT + ASYNC — make it post without being tagged using a scheduled cron job, event-watching, and self-scheduled follow-ups — and cap your token spend on day one. Plus the NO-CODE PATH (n8n: Slack Trigger → Anthropic Chat Model in the AI Agent node → Slack send; Make.com works the same), and the honest constraints (shared identity, a true ambient loop, security scoping and cost) that make Claude Tag genuinely hard to fully replicate. Verified against anthropic.com/news/introducing-claude-tag, Slack's Bolt + MCP docs, and n8n's docs (June 2026).

Subscribe to Hyperautomation AI ReportGet the PDF freeKeyword: SIDEKICK

By submitting, you'll be subscribed to the Hyperautomation AI Report newsletter — one practical AI email per week. Unsubscribe anytime.

Free. No spam. Unsubscribe anytime.