[Feature Request] Cross-device identity: account-bound memory across multiple machines

Problem

I'm a small business owner and PM working across a desktop, two laptops, and an iPhone. I use Claude Code on my primary machines and Claude Desktop and the iOS app on the others — but I'm working on the same projects across all of them.

The fundamental issue isn't sync. It's identity. Claude Code has no concept of "this user" — only "this filesystem path." Every device is a completely separate context, even when I'm working on the same client project. I'm constantly asking: which device has the right context? Does it have the full project identity this session needs?

I've cobbled together workarounds: pushing projects to Dropbox, writing aggressively to memory, maintaining a private Git repo to carry state. It's brittle. Paths change between machines, Dropbox sync locations differ, and I spend more time managing Claude contexts than using Claude.

Root Cause

Memory is keyed on the absolute filesystem path — stored under ~/.claude/projects/<encoded-absolute-path>/memory/. Same project, different machine = different key if the username, mount point, or sync path differs. This is documented in #25739. The git remote URL — which would be a stable cross-device identifier — is not used.

What's Been Tried

• autoMemoryDirectory (shipped v2.1.74, March 12, 2026) lets you redirect memory storage to a custom path (e.g., Dropbox), but doesn't address the identity problem natively and breaks when sync paths differ.
• Community tools exist — claude-context-sync, claude-sync, user-memories (the last using git remote URL as key) — but these are evidence of demand, not a solution.
• claude.ai already has cloud-synced, account-bound memory. Claude Code does not. These two systems are disconnected despite sharing an Anthropic account.

The Ask

Basic: Native support for account-bound, shared project identity in Claude Code — context and memory tied to the user's Anthropic account rather than the local filesystem path. Opt-in per-project, not global by default.

Dream: Full context portability across the entire Claude surface — claude.ai, Claude Code, Claude Desktop — so a user's identity and project context follow them wherever they work.

Related Issues

• #25739 — Portable project memory across machines (multi-device workflow) — OPEN
• #14228 — Claude Code should access user's claude.ai memory — OPEN
• #14227 — Persistent memory between Claude Code sessions — OPEN