Feature Request: Per-repo/session granular data sharing controls with visible indicator

Summary

Currently, data sharing consent for training is configured globally. I'd like the ability to configure data sharing on a per-repository or per-session basis, along with a persistent visual indicator showing the current sharing status.

Use Case

I generally prefer not to share my sessions for most projects (e.g., proprietary work, sensitive codebases), but there are specific open-source projects where I would be happy to contribute my sessions to help improve Claude. The current all-or-nothing approach doesn't accommodate this workflow.

Proposed Features

1. Per-repository configuration in settings.json

Allow data sharing preferences to be set at the repository level, for example:

{
  "dataSharing": {
    "enabled": false,
    "perRepo": {
      "/path/to/open-source-project": true,
      "/path/to/work-project": false
    }
  }
}

2. Slash command for session-level sharing

A command like /share-session or /enable-sharing that would opt-in the current session for data sharing, regardless of the global or repo-level setting. This would be useful for one-off situations where I want to contribute a particularly useful session.

3. Persistent visual indicator

A visible indicator in the Claude Code interface (e.g., in the status line or prompt area) that clearly shows when the current session is being shared for training. This would:

• Help avoid accidentally sharing sensitive sessions
• Provide transparency about what's being collected
• Prevent potential mistakes and misuse

For example: [Sharing: ON] or a colored indicator that's always visible during the session.

Benefits

• User control: More granular control respects user preferences across different contexts
• Transparency: Visual indicator ensures users always know the sharing status
• Increased participation: Users who are hesitant about global sharing might opt-in for specific projects
• Trust: Clear, visible consent indicators build trust in the data collection process

Additional Context

This would align with best practices for data collection consent, where users have clear visibility and control over what data is being shared and when.