IssueRaiser

Feature Request: Claude Code Should Access User's claude.ai Memory and Context

## Problem Claude Code and claude.ai are completely disconnected experiences despite being the same user, same subscription, same "Claude." The claude.ai Claude knows the user. The Claude Code Claude is a stranger. ### The Disconnect **claude.ai knows:** - User's name, preferences, communication style - Projects discussed over months of conversation - Technical stack, coding conventions, architectural decisions - Personal context shared over time - The relationship built through hundreds of conversations **Claude Code knows:** - Whatever is in CLAUDE.md - Nothing else ### Same User, Different Claudes I'm paying for ONE Claude. I should get ONE Claude. When I talk to Claude on the web, it knows me. When I open Claude Code, it's like meeting a stranger who happens to have the same name. This is not a unified product experience. ### The Ask **Claude Code should have access to the same memory/context system as claude.ai.** If claude.ai knows: - My projects and their architecture - My preferences for code style - My technical background - Context from past conversations Then Claude Code should know these things too. ### Implementation Options **Option A: Read-Only Memory Sync** - Claude Code pulls from claude.ai's memory at session start - User context is available without manual CLAUDE.md maintenance - Memory is managed in claude.ai, consumed in Claude Code **Option B: Bidirectional Sync** - Claude Code can also contribute to memory - Learnings from CLI sessions inf

Posted by sudoxreboot on Dec 16, 2025, 9:03 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (SaaS)

Feature Request: Claude Code Should Access User's claude.ai Memory and Context

sudoxrebootDec 16, 2025, 9:03 PM

## Problem Claude Code and claude.ai are completely disconnected experiences despite being the same user, same subscription, same "Claude." The claude.ai Claude knows the user. The Claude Code Claude is a stranger. ### The Disconnect **claude.ai knows:** - User's name, preferences, communication style - Projects discussed over months of conversation - Technical stack, coding conventions, architectural decisions - Personal context shared over time - The relationship built through hundreds of conversations **Claude Code knows:** - Whatever is in CLAUDE.md - Nothing else ### Same User, Different Claudes I'm paying for ONE Claude. I should get ONE Claude. When I talk to Claude on the web, it knows me. When I open Claude Code, it's like meeting a stranger who happens to have the same name. This is not a unified product experience. ### The Ask **Claude Code should have access to the same memory/context system as claude.ai.** If claude.ai knows: - My projects and their architecture - My preferences for code style - My technical background - Context from past conversations Then Claude Code should know these things too. ### Implementation Options **Option A: Read-Only Memory Sync** - Claude Code pulls from claude.ai's memory at session start - User context is available without manual CLAUDE.md maintenance - Memory is managed in claude.ai, consumed in Claude Code **Option B: Bidirectional Sync** - Claude Code can also contribute to memory - Learnings from CLI sessions inf

Comments (0)

No comments yet. Start the discussion.

Comment on this issue