Updated Aug 26, 2026 — Anthropic emailed Team and Enterprise customers this week with rollout specifics beyond the August 25 launch: admin defaults in Organization settings → Capabilities, a September 9 legacy export deadline, and hard blocks on government IDs and AUP violations. This post incorporates those details.
August 25–26, 2026 — Anthropic merged Claude Chat and Claude Cowork into a single memory layer across cloud, web, desktop, and mobile. Context you build in months of chat — project priorities, naming conventions, stakeholder prefs — is supposed to appear the moment Cowork takes a multi-hour task, and Cowork learnings flow back without re-briefing.
The second change matters for builders: memory updates while you work, not only when a session ends. Long Cowork runs that stretch across hours or days finally get mid-flight recall — the same problem memory.md patterns solve in repo-local agents.
TL;DR — what people are asking
| Question | Answer |
|---|---|
| Launch date? | Rolling out August 25–26, 2026 |
| What's unified? | Chat ↔ Cowork on cloud, web, desktop, mobile |
| Live updates? | Yes — individual topics during conversation |
| User control? | View / edit / delete topic list in Settings → Memory |
| Voice command? | Say "remember this" for explicit saves |
| Team/Enterprise default? | Memory available for org, off for end users until admin enables |
| Sensitive topics? | Off at admin level — hidden until Organization settings → Capabilities |
| User opt-in for sensitive? | Only after admin enables; then each user opts in individually |
| Existing memories? | Carry over, including sensitive topics already stored |
| Never saved? | SSNs, government IDs, criminal history, immigration status, AUP violations |
| Legacy export deadline? | September 9, 2026 — Settings → Memory → Export legacy memory |
Why Anthropic merged the silos
Before this update, Cowork memory stayed project-scoped while Chat memory was separate — so planning in chat did not automatically inform Cowork budget spreadsheets, and Cowork discoveries did not return to chat without copy-paste.
Anthropic's framing: Chat and Cowork should feel like one assistant as the company bridges Cowork into Chrome and desktop surfaces.
The New Stack noted the theme: months of convergence between conversational UI and computer-use agents.
What Team admins should configure before rollout
For Team and Enterprise workspaces, the August 26 email clarifies a two-layer gate most consumer posts skip:
- Memory is available for the org but off for end users by default. Admins must explicitly enable memory before anyone in the workspace sees topic generation or the Memory settings panel light up.
- Sensitive-topic memory is a separate admin toggle under Organization settings → Capabilities. Until an admin enables it, users do not even see the option to opt into health, religious beliefs, or political views — the UI stays hidden.
Practitioner checklist before you announce rollout:
| Step | Where | Why it matters |
|---|---|---|
| Decide org-wide memory policy | Organization settings → Capabilities | End users cannot self-enable if admin leaves memory off |
| Review sensitive-topic policy | Same Capabilities panel | Legal/compliance may want sensitive topics permanently off |
| Communicate user opt-in flow | Internal wiki / Slack | After admin enables sensitive topics, each user still opts in individually |
| Audit existing memories | Settings → Memory (spot-check as admin) | Existing user memories carry over, including sensitive topics already stored — not a clean slate |
| Export legacy format if needed | Settings → Memory → Export legacy memory | Deadline September 9, 2026 |
| Pair with agent controls | Managed Agents memory stores, MCP auth | Product memory ≠ developer API memory — different admin surfaces |
This is adjacent to but separate from Claude Enterprise-managed MCP authorization — memory Capabilities govern what Claude remembers about users; connector auth governs what tools Claude can reach.
Sensitive-topic controls (admin first, user second)
On Free, Pro, and Max, Anthropic excludes health, religious beliefs, and political views from memory unless the user opts in via Memory settings — with in-product notice when those topics are saved.
On Team and Enterprise, the flow is stricter:
- Admin level: sensitive-topic memory is off by default and hidden from users until enabled in Organization settings → Capabilities.
- User level: even after the org enables it, each user must opt in individually in their own Memory settings.
Existing memories carry over — if a user already had sensitive topics stored under the prior system, those topics persist after the unified rollout. Admins auditing compliance should review Memory settings per user, not assume the new defaults wiped old data.
That is a product-policy choice, not encryption magic. Enterprise buyers should still run DLP review — cloud memory is not your VPC. The Memory Heist showed how hosted memory plus browsing tools can leak PII even when users behave normally.
What Claude will never save
Anthropic's email draws a hard line on categories that never enter memory regardless of plan or opt-in:
- Social Security numbers
- Government IDs
- Criminal history
- Immigration status
- Acceptable Use Policy violations
When Claude encounters content in a blocked category, it tells the user it cannot save — not a silent drop. That is narrower than "sensitive topics" (health, beliefs, politics) which are user- or admin-gated. Teams writing internal AI policies should treat blocked categories as non-negotiable and sensitive topics as org-configurable.
Export legacy memory before September 9, 2026
Anthropic is replacing the prior memory format with the unified topic list. Users who want a copy of data stored under the legacy memory system should:
- Open Settings → Memory
- Select Export legacy memory
- Complete the export before September 9, 2026
After that date, the legacy export path closes. This matters for users who relied on the old end-of-conversation summary format and want an archive before migrating to editable topic lists. It does not block normal use of the new system — only the one-time legacy dump.
What this means for what you build or pay
Cowork power users: Less re-explaining Q3 goals when kicking off document-generation tasks — see top Cowork use cases for workflows that benefit most.
Claude Code teams: Do not confuse hosted memory with git-tracked CLAUDE.md — coding agents still need repo context, hooks, and loop engineering for reproducible builds.
Privacy: Free-tier users remain enrolled in training by default on Chat unless opted out — memory is adjacent but separate; check Anthropic's data settings if client work is sensitive. For Cowork-specific guardrails, see how to use Claude Cowork safely.
Claude cloud memory vs harness memory
| Layer | Scope | You control via |
|---|---|---|
| Unified Chat/Cowork memory | Anthropic cloud topics | Settings → Memory |
| CLAUDE.md / AGENTS.md | Repo / project files | Git, code review |
| memory.md / Obsidian vaults | Local-first graphs | Your filesystem |
| MCP resource stores | Tool-specific | Server config |
Use cloud memory for personal continuity; use files for team reproducibility.
Honest limitations
- Team/Enterprise is admin-gated twice — memory off for users until Capabilities enable; sensitive topics hidden until a second admin toggle.
- Existing sensitive memories persist — new defaults do not erase topics already stored.
- Legacy export window closes Sept 9, 2026 — miss it and you lose the one-click legacy dump.
- Not Claude Code session memory — developers still hit separate context windows in terminal harnesses.
- Not Managed Agents memory stores — API/agent memory is a different product surface with its own mount paths.
- Mobile requires app update — iOS/Android on latest build.
- Blocked categories ≠ all PII — employer name or hometown can still land in memory; see Memory Heist for exfiltration risk.
Related on explainx.ai
- Top 10 Claude Cowork use cases
- How to use Claude Cowork safely
- Claude Managed Agents memory on self-hosted sandboxes
- Claude Memory Heist — web_fetch PII exfiltration
- Claude Enterprise-managed MCP authorization
- Claude platform computer use GA
- What is memory.md for agents?
- What is CLAUDE.md?
- Loop engineering for coding agents
Anthropic plan defaults, Capabilities settings, and legacy export deadline accurate as of August 26, 2026 — confirm in Organization settings → Capabilities for Team/Enterprise admin policies.