Skip to content

Codex/release v0.5.2#51

Merged
Yurken merged 7 commits into
masterfrom
codex/release-v0.5.2
Jul 23, 2026
Merged

Codex/release v0.5.2#51
Yurken merged 7 commits into
masterfrom
codex/release-v0.5.2

Conversation

@Yurken

@Yurken Yurken commented Jul 23, 2026

Copy link
Copy Markdown
Owner

这个 Pull Request 推出了小妍桌面应用的 0.5.2 版本,重点改进了论文阅读与搜索体验、增强了缓存机制,并提升了错误处理的健壮性。本次更新还包含若干 Bug 修复,以及针对学术检索和专利检索工作流的优化。以下按主题分组列出最重要的变更:

功能增强:

  • 论文阅读器新增目录导航、文本标注和独立的问答侧边栏,使阅读、导航和笔记更加流畅。
  • 论文页面支持携带当前研究上下文,用户可以延续研究思路,将问题或线索直接带入协作对话中。

论文搜索改进:

  • 论文搜索现支持自然语言需求输入,系统会通过 LLM 自动将其拆分为多条搜索查询;若模型不可用,则回退到本地规则。高级搜索条件和字段步骤默认折叠,学术来源与网络来源合并展示、共享统一的截止日期,并持久化保存最近的输入和结果。
  • 搜索逻辑现采用截止日期(而非天数窗口),改进了日期归一化和校验。搜索查询会去重,多条查询的结果会合并,从而提升召回率和相关性。

缓存与性能:

  • 论文列表现在会复用缓存和快照,减少了在文献库和阅读器之间切换时的重复加载,导航速度更快。

错误处理与用户反馈:

  • 视觉模型请求失败时,现在会提供更清晰的配置检查提示,帮助用户诊断接口或模型问题。
  • 改进了论文搜索和 LLM 重排序的错误处理,提供更丰富的回退提示信息和日志记录。

Bug 修复:

  • 修复了实验代码消息显示的问题,并确保工作目录在实验切换和重新进入时保持持久化。
  • 改进了专利搜索和文档格式比对的逻辑,避免因否定表述、目录或普通格式差异导致的误判。

其他更新:

  • package.jsonCargo.toml、用户代理字符串和文档中的版本号更新至 0.5.2。
  • 更新了变更日志和自述文件,以反映 v0.5.2 的新功能和修复内容。

这些变更整体上提升了小妍桌面应用在学术研究场景下的易用性、效率和可靠性。

Copilot AI review requested due to automatic review settings July 23, 2026 01:55

Copilot AI 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.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@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: de33305c89

ℹ️ 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 +59 to +60
let model_plan_valid = planned.len() >= 2;
let queries = merge_queries(planned, fallback);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Preserve structured constraints in every query plan

When the LLM returns four valid queries, normalize_queries caps the concatenated list at four, so every locally generated fallback query is discarded. In that case an LLM response that omits a selected author, venue, category, or keyword causes the Semantic Scholar requests to run without that user-specified constraint; this is especially likely for the large venue lists produced by the domain filter. Reserve a fallback/constraint-bearing query or merge the structured terms into each planned query before applying the cap.

Useful? React with 👍 / 👎.

Comment on lines 226 to 227
} catch (nextError) {
setResult(null);
setError(formatErrorMessage(nextError));

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 Clear prior results when a new search fails

If a user changes the draft and the subsequent academic search fails (for example, due to a network error or an invalid persisted cutoff date), this catch only records the error and leaves session.result and session.webSupplement untouched. The panel therefore shows the prior query's papers and web sources beneath the new draft, and those stale results remain persisted across navigation; clear them at search start or in this failure path so the displayed data cannot be mistaken for the failed search's output.

Useful? React with 👍 / 👎.

@Yurken
Yurken merged commit 2957d51 into master Jul 23, 2026
6 checks passed
@Yurken
Yurken deleted the codex/release-v0.5.2 branch July 23, 2026 02:05
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.

2 participants