CommandCodeAI / CommandCodeAI/command-code

Feature request: Selective redaction before sharing a conversation

未关闭
#552 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
没有语言数据
星标
4k
派生
350
PR 合并指标
30 天内没有已合并 PR

描述

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

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

该 issue 未指定实现文件、测试或入口点;首先定位现有的 Share 流程,以及对话内容的组装方式。完成的标准是用户可以涂黑选定的或重复出现的敏感文本,预览共享版本,并保持原始对话不变。

由索引模型根据 Issue 内容生成。

评估

领域
cli
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。