[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

---
name: Feature Request - Unified Memory
description: Proposal for unified memory system across Claude Code tabs (Chat, Cowork, Code)
type: reference
originSessionId: f8939f09-a79c-40a5-a83a-b45b77aa671e
---

Unified Memory System Across Claude Code Tabs

Current Behavior

Each tab in Claude Code (Chat, Cowork, Code) maintains isolated memory. When switching tabs, the previous tab's context—including saved memories about projects, preferences, and state—becomes inaccessible to the new tab. This forces developers to either maintain separate memory files manually or re-establish context in each tab.

Problem

Working on a complex project (e.g., a live trading bot with multiple config files and status checks) requires switching between tabs frequently. Currently, switching from Chat to Cowork loses access to project-specific memory, forcing the developer to either:

• Recreate context by re-reading files
• Maintain parallel memory files outside the app
• Stay in a single tab, limiting workflow flexibility

Proposed Solution

Proposed Solution

Make the memory system global across all three tabs. All tabs should read from and write to the same unified memory store (~/.claude/projects/*/memory/), so context persists seamlessly when switching tabs.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Developer tools/SDK

Use Case Example

Benefit

Developers could move fluidly between Chat (for exploration/discussion), Cowork (for collaboration context), and Code (for implementation focus) without losing accumulated knowledge about the project.

Additional Context

_No response_