1. What to include in a product issue1. 产品 Issue 应包含什么
- Context Visualizer version and whether you use the desktop app or web tool;Context Visualizer 版本,以及你使用桌面版还是网页版;
- Windows version and x64 architecture confirmation for desktop issues;桌面问题请提供 Windows 版本并确认 x64 架构;
- the source type (Claude Code or Codex) and approximate session count or file size;来源类型(Claude Code 或 Codex)及大致会话数或文件大小;
- clear reproduction steps, expected behavior, and actual behavior;清晰的复现步骤、预期行为与实际行为;
- a sanitized screenshot or exact non-sensitive error message.经过脱敏的截图或准确的非敏感错误信息。
A minimal reproducible example is more useful than a full private project. Replace names, paths, excerpts, and identifiers before posting.最小可复现示例比完整私密项目更有用。发布前请替换名称、路径、摘录与标识符。
2. Never post these publicly2. 绝不要公开这些内容
- OpenRouter API keys, tokens, passwords, or environment files;OpenRouter API key、Token、密码或环境文件;
- raw Claude Code/Codex transcripts or confidential source code;原始 Claude Code/Codex transcript 或机密源码;
- full local paths containing personal names or private folder structures;含个人姓名或私密目录结构的完整本地路径;
- purchase email, order ID, invoice, card, identity, tax, or KYC information.购买邮箱、订单 ID、发票、银行卡、身份、税务或 KYC 信息。
If a key was exposed, revoke it in OpenRouter immediately and create a replacement with an appropriate spending limit.如果 key 已泄露,请立即在 OpenRouter 撤销并创建设有合理消费上限的新 key。
3. Privacy and security matters3. 隐私与安全事项
Do not disclose vulnerability details, personal data, or private project content in a public issue. For a non-purchase matter, open a minimal GitHub issue asking for a private follow-up and include no sensitive detail. For a purchase-related matter, use the private contact path in your Creem receipt or Customer Portal.不要在公开 Issue 中披露漏洞细节、个人数据或私密项目内容。非购买事项可创建一个不含敏感细节的最小 GitHub Issue,请求私下跟进;购买相关事项请使用 Creem 收据或 Customer Portal 中的私密联系路径。
The public branded support mailbox is not yet published. It will be added before live checkout if required by the Merchant of Record review. We do not publish a personal address or personal email as a substitute.公开品牌支持邮箱尚未发布。如 Merchant of Record 审核要求,将在生产结账前添加。我们不会用私人住址或私人邮箱冒充公开支持渠道。
4. Quick checks before opening an issue4. 提交 Issue 前的快速检查
- Confirm Windows 10/11 x64 and that the installer warning is the expected unsigned-beta reputation warning, not a different security alert.确认使用 Windows 10/11 x64,并区分预期的未签名 Beta 信誉警告与其他安全警报。
- Confirm your OpenRouter key is active, has balance, and has a sufficient spending limit.确认 OpenRouter key 有效、有余额且消费上限足够。
- Try one small, recent session before a large multi-session project.在大型多会话项目之前,先尝试一个较小且近期的会话。
- Check the selected provider’s status and policy if a model call fails.模型调用失败时,检查所选提供商的服务状态与政策。
- Keep the last audited map; do not delete source files while troubleshooting provenance.保留上一次通过审计的地图;排查来源回溯时不要删除源文件。
5. Current purchase status5. 当前购买状态
The Founding Beta price is one-time USD $39. Production checkout is not live while Creem merchant review is pending. The interactive web tool and public GitHub repository are available now. No legitimate purchase link will be presented as live until a production Creem checkout has been verified.Founding Beta 价格为一次性 39 美元。Creem 商户审核期间,生产结账尚未开放。交互式网页版与公开 GitHub 仓库现在可用;在真实生产 Creem 结账验证完成前,不会把任何购买链接标成已上线。