[FEATURE] Ability to resume conversations from outside and inside dev containers.

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

Sometimes I work on the same project with Claude Code both inside and outside a dev container. The paths differ:

• Outside: ~/projects/myproject/repos/myrepo1
• Inside: /myrepo1 (only the repo is mounted)

Claude Code keys project data in ~/.claude/projects/ by absolute path, so these create separate entries (e.g., -home-user-projects-myproject-repos-myrepo1 vs -myrepo1). This means conversations, memory, and settings are not shared between the two contexts, even though it's the same project and ~/.claude is bind-mounted into the container.

Proposed Solution

• Automatic detection that two paths point to the same git repository (same remote URL / commit history)
• A .claude/project-id file in the repo root that Claude Code uses as the key instead of the absolute path
• A project-alias field in .claude/settings.json that maps multiple paths to the same project data

Alternative Solutions

A symlink workaround is possible (ln -sfn ~/.claude/projects/-myrepo1 ~/.claude/projects/-home-user-...) but fragile — Claude Code can overwrite the symlink.

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

Start a conversation inside the dev container (at /myrepo1) working on a feature, then later open the same repo outside the container (at ~/projects/myprojects/repos/myrepo1) and want to continue that conversation or have access to the same project memory.

Additional Context

_No response_