Feature request: Selective redaction before sharing a conversation

Summary

When sharing a conversation, the entire thread is exposed as-is with no way to redact sensitive content first. If a shared conversation contains something like an API key, internal detail, or personal info mentioned mid-thread, there's currently no way to share the rest without exposing that too.

Expected Behavior

Before generating a share link, users should be able to enter a redaction/edit mode (e.g. toggled via an eye icon) that lets them select specific text — via click-drag/highlight — and mask it. Masked content would show as [redacted] only in the shared version, without altering the original conversation. Ideally this includes a preview step showing exactly what the recipient will see before the link is generated, and a "redact all instances" option for repeated sensitive strings (e.g. an email or key appearing multiple times).

Actual Behavior

Sharing currently copies the full conversation with no redaction option. Any sensitive text in the thread is fully visible to whoever receives the share link.

Steps to reproduce the issue

1. Have a conversation containing sensitive text (e.g. an API key or personal detail).
2. Use the Share feature to generate a link.
3. Open the shared link.
4. Observe that the sensitive text is fully visible with no option to have redacted it beforehand.

Command Code Version

Microsoft Windows [Version 10.0.26200.8737]
(c) Microsoft Corporation. All rights reserved.

C:\Users\USER>

Operating System

Windows

Terminal/IDE

Unknown

Shell

cmd.exe

Additional context

This came up after using the share/unshare feature — which is great — but I noticed the full conversation is exposed by default. Originally raised as a suggestion in this thread: https://x.com/CommandCodeAI/status/2075203122792902743
Here is my post
https://x.com/lordtechytro/status/2075426514032615668?s=20
https://x.com/lordtechytro/status/2075399315942445058?s=20

L’issue ne nomme aucun fichier d’implémentation, test ou point d’entrée ; commencez par localiser le flux Share existant et la façon dont le contenu de la conversation est assemblé. La tâche est terminée lorsque les utilisateurs peuvent masquer certains textes sensibles ou les textes sensibles répétés, prévisualiser la version partagée et laisser la conversation d’origine inchangée.