Skip to content

feat(qa): 独立 DeepSeek 管线、联网问答与持久会话 - #1440

Open
appergb wants to merge 11 commits into
betafrom
feat/deepseek-suite-web-search
Open

appergb wants to merge 11 commits into
betafrom
feat/deepseek-suite-web-search

Conversation

@appergb

@appergb appergb commented Nov 14, 2026 •

Copy link
Copy Markdown
Collaborator

Fn + Space 现在以普通问答为默认入口,仅在实际存在选区时附加选中文本。同一问答窗口在录音、处理中和失去焦点后保留内容,直到用户主动关闭;后续问题继续原会话,并通过独立胶囊显示“随便问”。组合键吞掉空格按下、重复和释放,普通空格正常传递。

DeepSeek 大统一作为识别管线的第三个独立模式,和传统、多模态并列。三种模式保持配置与选择;大统一首次复制已配置的默认官方 DeepSeek 渠道密钥,此后独立保存。只有大统一调用原生联网和流式朗读。传统、多模态使用独立 Web Search(默认免费 Bing RSS 与公开网页读取,也支持 Tavily、Brave、SearXNG 或关闭)。回答提示词明确实际搜索后端。正文末尾左侧显示带站点图标的来源编号,右侧为复制、套件模式限定的朗读,并提供减少动态效果支持。回答卡片使用实际布局尺寸;滚动跟随不会在内容变化时抢回用户的阅读位置。

macOS 辅助功能引导改用普通有边界窗口、系统语义颜色与原生文件拖拽控件,跟随系统设置定位,关闭时释放窗口和定时器。按键事件同步 Fn 当前状态,避免遗漏松开事件后误吞普通空格。

验证:

  • npm test(含 TypeScript、前端构建与前端测试)通过。
  • Core 1493 个单元测试及 38 个 Q&A 集成/合约测试通过;原生 Tauri 715 个测试通过;胶囊库 6 个测试通过。
  • Chromium/WebKit:三管线切换与关闭设置后保留选择、独立凭据、来源与复制/朗读布局、图片 CSP、减少动态效果、胶囊输入和既有动效覆盖;受第三管线影响的几何断言已更新并重跑通过。
  • macOS 原生引导定位、窗口标志、深浅色对比度与释放测试通过。独立 AppKit 测试窗口在引导显示和关闭后均可按窗口范围捕获;尚未复现用户报告的“全黑截图持续到重启”,不将该测试视为完整系统级根因验证。
  • macOS、Windows、Android、iOS、Harmony 与两套浏览器的 完整 PR CI 已通过。新版 macOS ARM64、macOS Intel 和 Windows x64 安装包构建 均已成功。三个安装包已下载,完成归档摘要、架构、macOS DMG/代码签名与 Windows 来源/更新签名核验;仅交付本地分支测试包,不发布 release。

接口与兼容性见 docs/deepseek-suite.md。新增独立凭据保留在本地 vault;服务端仍接收现有不透明加密同步文档,无新增服务端 API。

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T14:33:41.210209Z 97ce447 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@appergb appergb changed the title feat(qa): 接入 DeepSeek 大统一与自主联网搜索 feat(qa): 独立 DeepSeek 管线、联网问答与持久会话 Nov 14, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f26baa5995

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +2322 to +2323
if let Err(error) = inner.backend.services().qa.cancel(None).await {
log::warn!("[coord] QA cancellation from Escape failed: {error}");

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Exclude cancelled QA turns from subsequent Escape routing

On Windows, cancelling a voice question with Escape now leaves the QA snapshot in QaPhase::Cancelled instead of dismissing it and resetting it to Idle. The qa_active predicate immediately above still treats every non-Idle phase as active, so subsequent Escape events forwarded from the main window keep entering this branch—even after ordinary dictation has started—and never reach cancel_active_session. This also occurs when the question was cancelled before the QA panel appeared, leaving no visible panel to dismiss. Restrict QA ownership to active phases (plus a visible panel) so a cancelled, hidden question cannot consume later dictation cancellation.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant