Help & support帮助与客服 User manual用户手册 Features功能 GitHub →

CC POCKET SUPPORTCC POCKET 客服

Ask a question.
Get unstuck.直接提问，
快速解决。

Smart support searches the maintained CC Pocket knowledge base and gives you a practical next step. It is public: no account, sign-in, or organization membership is required.智能客服会检索持续维护的 CC Pocket 知识库，并给出可执行的下一步。它完全公开，无需账号、登录或加入任何组织。

Ask smart support咨询智能客服 Browse the manual浏览用户手册

Public support is online · no sign-in required公开客服在线 · 无需登录

CC Pocket Supportpublic · manual-grounded公开 · 基于用户手册
SUPPORT

Hi — tell me what you want to do or what went wrong. I can search the CC Pocket manual and walk you through the next step.你好，请告诉我你想完成什么，或遇到了什么问题。我会检索 CC Pocket 用户手册，并引导你完成下一步。

Enter to send · Shift+Enter for a new line回车发送 · Shift+回车换行

Do not send keys, tokens, pairing codes, private code, or unredacted logs.请勿发送密钥、令牌、配对码、私有代码或未脱敏日志。

CHOOSE A PATH选择解决方式

Use the route that fits.选择适合你的解决方式。

01

Ask smart support咨询智能客服

Describe the symptom in your own words. The public support agent will search maintained CC Pocket guidance.用自己的话描述现象，公开客服 Agent 会检索持续维护的 CC Pocket 指南。

Start a conversation开始对话 → 02

Browse the user manual浏览用户手册

Task-based guides for setup, sessions, approvals, agents, sharing, privacy, and troubleshooting.按任务查找安装、会话、审批、Agent、共享、隐私与故障排查步骤。

Open public manual打开公开手册 → 04

Report a reproducible issue报告可复现问题

Use GitHub when the answer should become a tracked bug, feature request, or public discussion.需要跟踪缺陷、功能建议或公开讨论时，请使用 GitHub Issue。

Create an issue创建 Issue →

BEFORE YOU SEND发送问题前

Share the symptom, not the secret.描述现象，不要发送秘密。

  • Never send API keys, pairing codes, access tokens, private keys, or full environment files.不要发送 API Key、配对码、访问令牌、私钥或完整环境变量文件。
  • Redact repository names, paths, logs, and screenshots that contain private project data.发送仓库名、路径、日志或截图前，先遮盖私有项目数据。
  • For security vulnerabilities, use a private GitHub security advisory instead of a public issue.安全漏洞请通过 GitHub 私密安全公告提交，不要发布公开 Issue。