Feedback Request: Project-Scoped Search (v2.4.3 Breaking Change)

[ramakay]

Overview

In v2.4.3, we introduced project-scoped search as the default behavior. This is a breaking change that significantly alters how search works in Claude Self-Reflect.

What Changed

Before v2.4.3:

• Searches looked across ALL your projects by default
• You would get results from every conversation you've ever had

After v2.4.3:

• Searches are limited to your current project directory
• Cross-project search requires explicit request

Why We Made This Change

1. Focus: When working on ProjectA, results from ProjectB are usually noise
2. Performance: Searching one collection is ~100ms faster than searching 20+
3. Privacy: Work and personal projects stay naturally isolated
4. Intuitive: Most users expect search to be contextual to their current work

How to Use It

# Default: Current project only
"What did we discuss about authentication?"

# Search everywhere (old behavior)
"Search all projects for authentication"

# Search specific project
"Find auth code in MyApp project"

Questions for the Community

1. Is this change helpful or disruptive to your workflow?
2. Do you find yourself needing cross-project search often?
3. Should we add a config option to restore the old behavior as default?
4. Any edge cases or issues you've encountered?

Additional Context

This change partially addresses issue #14 (selective project import). While that issue requested the ability to exclude projects from import entirely, project-scoped search solves the core problem of result noise.

Share Your Feedback

Your input helps shape the future of Claude Self-Reflect. Please share:

• Your experience with the new behavior
• Any confusion or friction points
• Suggestions for improvement
• Whether the breaking change was worth it

Detailed documentation: Project-Scoped Search Guide