Answer questions about dsh-tui using its bundled manuals. Find relevant guidance on installation, shortcuts, configuration, themes, session migration, and VS Code integration, then cite the source file and section for checking.
Use when the user asks about dsh-tui itself (usage, shortcuts, config, themes, migration, VS Code). Load before answering; skip for normal coding tasks.
Review the instructions the agent will receive before you install.
用户手册全文就在本文件所在目录——skill 工具返回的 resourceBase。共 10 篇，
每篇中英各一份：中文文件名无后缀，英文加 .en.md。拿不到绝对路径时，用
glob 在 dsh-tui 包里搜 guide/dsh-tui-guide。
grep 关键词拿到命中行，
再用 read 带 offset/limit 只展开需要的那几段。| 用户问的 | 文件 |
|---|---|
| 安装、首次启动、启动失败、排障 | getting-started.md |
| 日常使用、键位、斜杠命令、会话与工作流、设置 | user-guide.md |
| 输入框、鼠标、选中复制、粘贴、图片、问卷与审批 | interaction.md |
| 配置覆盖层、TUI 开关、agent preset、模型路由、MCP | configuration.md |
| Claude 后端：启用、登录、与 DSH 的差异、已知限制 | claude-backend.md |
| Codex 后端：安装、登录、渠道、Plan、会话与原生能力 | codex-backend.md |
| 主题、配色、自动检测、自定义主题 | themes.md |
| 从 Claude Code / Codex / OMP / zcode / Grok 迁移会话 | migrate.md |
| 无界面执行、JSON 输出、CLI 会话查询与官方转接 | cli.md |
| VS Code 集成、扩展、IDE 选区 | vscode.md |
| 插件生态、接缝稳定性分级 | plugins.md |
英文提问时把上表文件名接上后缀（例如 user-guide.en.md）。
除本文件外，这些副本由
scripts/build-guide.mjs从仓库docs/逐字节同步生成， 不要手改；改文档请改docs/再跑一次构建。
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit a repository or broad subsystem for security, correctness, and maintenance risks. Trace how inputs reach affected behavior, verify suspected defects, and report confirmed findings with severity, triggers, impact, and practical remedies.
Turn a reported defect into a concise bug report or issue draft that someone else can reproduce or investigate. Organize symptoms, reproduction steps, expected and actual behavior, environment, and impact while separating evidence from unknowns.
Prepare and publish a pull request with a linked issue, English commit and PR titles, and a Chinese description explaining the change, implementation, and verification. Update an existing branch PR and report its URL and CI status.
Turn existing pull request review comments into prioritized next steps by checking them against the current code. Separate outstanding concerns, addressed feedback, and questions needing replies, then implement and validate fixes when requested.
Practice one programming concept through a small exercise matched to your goals, experience, and available time. Get feedback based on observable results, with hints or explained solutions and a harder variation when you are ready.
Draft release notes that explain what changes for users. Verify the release range, reconcile commits and reversals, and highlight breaking changes, migration steps, and relevant pull requests with evidence.