docs: 扩充 FAQ 性能/委派/自动化章节，修复 More 索引 - #38
Conversation
FAQ 改进: - 06-performance.md: 从 2 题扩充到 7 题（磁盘、GPU、资源查看等） - 新增 07-delegation.md: 委派与协作 FAQ（7 题） - 新增 08-automation.md: 自动化 FAQ（7 题） - index.md: 添加新分类链接 More 改进: - index.md: 添加第三方软件与许可链接（zh+en） 截图: - 添加 DesireCore 主界面真实截图 i18n: - 同步更新英文版 FAQ（06-performance 扩充、07-delegation、08-automation 新增） - 同步更新英文版索引
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 26e2d36185
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| 1. **确认调度存在** --- 使用 ManageSchedule（action=list）查看调度列表，确认任务未被删除或取消 | ||
| 2. **检查触发时间** --- 确认 trigger_value 的时区正确（使用带时区的 ISO 格式，如 `2026-07-26T09:00:00+08:00`） | ||
| 3. **检查应用是否运行** --- 调度需要 DesireCore 在运行中才能触发；应用关闭期间到期的调度会在下次启动后补触发 |
There was a problem hiding this comment.
This guarantee is false when a schedule uses the documented skip missed-fire policy: docs/02-user-guide/08-automation/03-scheduled-tasks.md:268-280 says only missed interval runs are detected for compensation and that missed_fire_policy determines whether they run at all. A user relying on this FAQ may close the app expecting a reminder or job to execute on restart even though it is skipped. Describe the policy-dependent behavior here and in the English mirror.
Useful? React with 👍 / 👎.
| 2. **使用 notify=false** --- 无变化时静默记录，不发送通知 | ||
| 3. **优化检查逻辑** --- 只在确实有变化或需要关注时才设置 notify=true |
There was a problem hiding this comment.
The documented heartbeat contract does not expose a notify configuration flag: HeartbeatRespond submits an outcome and optional notificationText, and no_change is the outcome that records silently (docs/02-user-guide/08-automation/01-heartbeat.md:66-86). Consequently, setting notify=false or notify=true as suggested here will not adjust notification behavior. Direct users to return no_change or the appropriate structured outcome, and update the English mirror as well.
Useful? React with 👍 / 👎.
…mage - Rename 09-third-party-software.md → 10-third-party-software.md to eliminate duplicate 09- numbering with 09-open-source-repos.md (file content unchanged, originally added in PR #29 commit 18d6617) - Rename 10-changelog/ → 11-changelog/ for sequential numbering - Update all 14 cross-references (zh + en) to new paths - Remove unreferenced docs/06-faq/assets/desirecore-main-interface.png
修复 PR #35 审核反馈： - 删除误提交的 PLAN-interface-conversations.md - 还原 interface/conversations/super-document/memory/capabilities/email/ concepts/more/faq 章节至 origin/main（由 PR #36/#38 各自负责） - 移除 .drawio 源文件（keyboard-shortcuts-overview, data-flow-diagram） - 移除不属于本 PR 的 static/img 图片文件 - 移除 FAQ 中越界新增的 07-delegation.md、08-automation.md 本 PR 现仅包含 user-guide/06-agents/ 和 03-teaching/ 的内容增强。
There was a problem hiding this comment.
💡 Codex Review
Update changelog consumers after renaming the directory
This rename removes docs/05-more/10-changelog, but the Docusaurus plugin in plugins/changelog-json-plugin.ts still passes that path to readdirSync during loadContent, so every site start/build aborts with ENOENT before generating the documentation. The cover-generation scripts also retain the old Chinese and English paths; update all hard-coded consumers to 11-changelog as part of the move.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
- plugins/changelog-json-plugin.ts: fix build-breaking path reference - scripts/backfill-en-covers.mjs: fix utility script path - scripts/generate-changelog-cover.mjs: fix utility script path
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 36f0b299fc
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| 1. 在智能体的对话历史中找到对应时间的会话记录 | ||
| 2. 调度触发时的 prompt 会作为该会话的第一条消息 | ||
| 3. 如果调度执行失败，可以在会话记录中看到错误信息 |
There was a problem hiding this comment.
For triggers whose result is stored only as an execution record, there may be no corresponding conversation to find: the scheduled-task guide says results can enter a conversation, notification, or execution record, while every trigger—including failed and skipped runs—is recorded in the task detail's execution history (docs/02-user-guide/08-automation/03-scheduled-tasks.md:282-306). Direct users to Automation → task details → execution history rather than presenting conversation history as the way to inspect runs, and update the English mirror as well.
Useful? React with 👍 / 👎.
1 participant
修改内容
FAQ 扩充（中文 + 英文）
More 完善（中文 + 英文）
截图
真实性说明
未修改