CommandCodeAI / CommandCodeAI/command-code
Feature request: Selective redaction before sharing a conversation
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
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
- Have a conversation containing sensitive text (e.g. an API key or personal detail).
- Use the Share feature to generate a link.
- Open the shared link.
- 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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no implementation files, tests, or entry points; begin by locating the existing Share flow and how conversation content is assembled. Done means users can redact selected or repeated sensitive text, preview the shared version, and leave the original conversation unchanged.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100