[FEATURE] Enable Cross-Project Conversation Search and Context Access

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

When I'm working in a Claude Project, the conversation_search and recent_chats tools can only access conversations within that specific project. This creates a significant workflow barrier when I want to:

• Continue work from a previous conversation that occurred outside of projects
• Bring context from other projects or general conversations into my current project
• Organize existing work into a project structure after the fact

Proposed Solution

I would like the ability for Claude to access and search conversations outside of the current project when working within a project environment.

Add an option or permission setting that allows Claude to search and reference conversations across project boundaries when the user explicitly requests it. This could be:

• A toggle in project settings to "Allow access to conversations outside this project"
• A prompt when searching that asks "Would you like me to search outside this project too?"
• A separate search parameter like "search_scope: all" vs "search_scope: current_project"

Benefits:

• Seamless continuation of work across organizational boundaries
• Better project organization without losing access to previous context
• Reduced friction when transitioning from exploratory conversations to structured project work
• Maintains the value of conversation history while enabling better organization

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

Other

Use Case Example

I had an extensive conversation about "Forecasting", and this was outside of any project. The conversation became very large (code, iterations, problem statements, frameworks, etc.) and reached the message limit. When I tried to continue this work within a project, Claude couldn't access the original conversation because it was outside the project boundary.
This forced me to either:

• Exit the project and work outside of projects entirely (losing organizational benefits)
• Manually copy/paste massive amounts of context (time-consuming and error-prone)
• Summarize and lose critical details (defeats the purpose of conversation history)

Additional Context

_No response_