Skip to content

文枢 v0.6.0

Latest

Choose a tag to compare

@zgdllt zgdllt released this 12 Nov 05:25

文枢 v0.6.0

The app becomes 文枢 — it remembers the unfinished work for you. The question-first workbench of v0.5 stopped being answered by day three (249 pending items and 226 open questions after a week), so v0.6.0 lets the agent maintain the state itself and interrupts you only when it matters. The previous workbench stays available at /classic.

Changes

  • Four-quadrant board. 先做 / 安排时间 / 顺手处理 / 放一放. Urgency comes from dates; importance is learned from feedback. Undated tasks nest under their projects, duplicates across Calendar, Reminders and agent clues merge, and low-confidence clues stay off the board. Drag to recalibrate; every change can be undone.
  • Notifications with buttons and a reply box. Only 先做 items, plus at most one "may have forgotten" item a day; no repeats within 12 hours; quiet hours 22:00–09:00 by default (configurable). 开始 / 已完成 / 稍后 / 不重要 act in place.
  • Replies are understood immediately. A typed reply is classified (done, not important, later, doing, blocked, became a tool, waiting, reschedule, new task, note) by the configured model. Status changes apply at once; reschedules and new tasks become proposals on the card that you accept or reject. Unparseable replies, missing providers and model failures keep the text as a note.
  • Profile-driven daily inference. With a provider configured, project stages are re-read against your own-words profile once a day after 09:00, in a detached process. Inferred stages still ask for one confirmation. The memory page shows the last run.
  • 文枢's own calendar and reminder list. gtd.py setup-owned (or Settings) creates a "文枢" calendar and list on your default account. 文枢 updates its own items directly, with version checks and idempotent receipts; your own lists keep the preview-and-confirm path. Accepting a reschedule on your own calendar event changes only 文枢's view, and the UI says so.
  • Provider fix. Instructions are now sent at the start of the user message. Some OpenAI-compatible gateways silently drop system prompts, which made models ignore the JSON contract. Set "system_role": true in a provider file to restore the old layout.

Downloads

  • Getting-Things-Done-v0.6.0-macos-arm64.zip — macOS 14+ Apple Silicon app with the precompiled EventKit bridge. Requires Python 3.11+.
  • Getting-Things-Done-v0.6.0-source.zip — matching source, tests and documentation.
  • SHA256SUMS — checksums for both archives.

Private data and model settings remain in their existing locations; the board and memory are built from them on first launch. The app is ad-hoc signed and is not notarized. Rebuilding the native bridge can reset macOS calendar/reminder access to "not determined"; run gtd.py authorize again if prompted.

Verification

254 unit tests (board, merge, notifications, reply understanding, proposals, daily inference, owned calendar, providers) pass with isolated state and mocked models; no real model calls or Apple writes are needed. The workbench, cards and files browser regressions pass with zero browser errors. Reply understanding was also checked against a real DeepSeek-compatible endpoint (9 of 9 typical replies classified correctly, including an injection attempt kept as a note). The packaged app was extracted to a different path: its strict code signature verifies, both native executables are arm64, and its own bundled web resources render the 文枢 board (four quadrants; 看板 / 记忆 / 设置) against synthetic state with zero browser errors. The native WKWebView launch check (verify_packaged_app.py) could not run in this build environment because of a macOS sandbox restriction that also blocks the same check for the published v0.5.1; the same code has been running as the installed app on the developer's Mac since 2026-11-12. Notarization and physical mobile-device acceptance are outside this release's verification.