🧭 Claude Tag Replaces the Classic Slack App Tomorrow — Here's What Changes
From August 3, 2026, Claude Tag replaces the legacy "Claude in Slack" app on Claude Team and Enterprise plans. The transition isn't cosmetic: Claude Tag is a fundamentally different model of how AI participates in a Slack workspace — one Claude agent per channel, shared and visible to everyone in that channel, rather than each user getting their own private Claude session.
How Claude Tag works
- @Claude in any channel to delegate a task. Claude breaks the work into stages, runs them sequentially (using whichever tools admin has approved for that channel), and replies in a thread.
- Shared context: teammates can see what Claude is doing and pick up the thread mid-task, treating it like shared work rather than a private assistant.
- Ambient mode: when enabled, Claude proactively flags relevant information and follows up on stalled threads without being explicitly tagged.
- Isolated identities: admins configure a different Claude identity per channel — separate tool access, separate memory, separate spend limits — so your #security-review channel can't reach the same data as #marketing.
- Direct messages: users can still message Claude privately with personal tool configurations.
Admins: the migration window is now
The 30-day window opened when Claude Tag launched in beta on June 23. The automatic switchover happens tomorrow (August 3). If you haven't migrated yet, review which channels should have Claude Tag enabled and which tools each channel should be able to reach before the cutover. Channel-level tool scoping is the key new configuration surface — it doesn't exist in the legacy app.
Anthropic has noted that 65% of their own product team's code is now generated through their internal Claude Tag deployment — a meaningful signal about how seriously they're leaning on this pattern internally.
Claude Tag
Slack
Team
Enterprise
agent
migration
🧭 AI for Science Rare Disease Grants Close Tonight — Up to $50,000 in Claude Credits
Anthropic's AI for Science rare disease research grant program closes tonight at 11:59 PM PST. Selected researchers and early-stage biotechs receive up to $50,000 in Claude credits over six months to accelerate work on rare genetic conditions. If you or anyone on your team is working in this space, today is the last day to apply.
Two tracks
- Track 1 — Basic Science Partnerships: collaborations between clinical researchers, patient organisations, and data scientists. Funded projects might reveal mechanistic disease links, curate patient data for natural history studies, or build evaluations measuring AI model performance on rare disease tasks. Outputs are published through the Monarch Initiative.
- Track 2 — Biotech Acceleration: early-stage biotechs working to shorten drug development timelines — dose justification from limited data, biomarker identification from case reports, regulatory documentation drafting. Anthropic estimates this could compress months of dossier assembly into days.
Who's already working in this programme
Existing grantees include Every Cure (drug repurposing opportunities via Claude), the Centre for Population Genomics (Claude-based variant classification systems), and the Violet Research Institute (navigating FDA guidelines for ultra-rare disease regulatory submissions).
Honest about the limits
The programme page openly acknowledges where AI doesn't help: extremely limited datasets, poorly organised data, insurance authorisation challenges, and diagnostic infrastructure access. That candour is notable — it positions this as targeted scientific acceleration rather than a blanket "AI solves rare diseases" claim.
AI for Science
grants
rare diseases
biotech
research
deadline
🧭 Console Workbench Sunset: Export Your Saved Prompts Before August 17
The legacy Workbench at platform.claude.com/workbench loses access on August 17, 2026 — two weeks from today. Critically, saved prompts, variables, and evals do not carry over to the updated Playground at platform.claude.com/playground. If you've accumulated prompt libraries or eval suites in the old Workbench, you need to export them now.
What's going away
- The legacy Workbench UI and all saved content within it
- The experimental prompt tools APIs:
/v1/experimental/generate_prompt, /v1/experimental/improve_prompt, and /v1/experimental/templatize_prompt — requests to these endpoints will return errors after August 17
How to export before the deadline
Anthropic provides two export paths: the dismissible banner that appears at the top of the legacy Workbench, or via Organizational Settings in the Claude Console. The new Playground covers the core interactive testing workflow; teams relying on programmatic prompt generation via the experimental APIs will need to replicate that capability in their own tooling.
# After August 17, this returns an error — migrate before then
POST /v1/experimental/generate_prompt
POST /v1/experimental/improve_prompt
POST /v1/experimental/templatize_prompt
Check your CI/CD pipelines and internal tooling
The experimental APIs were occasionally used in automated prompt-refinement pipelines. If any of your team's scripts or workflows call these endpoints, they will break silently (returning errors instead of prompts) after August 17. Audit your codebase for these endpoint strings now.
Workbench
Console
sunset
migration
prompt APIs
August 17
