Pacenote v0.5.7

Tasks in Todo now follow their threads: when a thread moves a due date, sharpens the ask or names the repository, the next collection updates the task and says why. The open row says less, too.

brew update && brew upgrade --cask pacenote

The upgrade quits the running app first and reopens it, once. Config, run history and your tasks are untouched.

Apple silicon only

Intel Macs are no longer supported. This release and later are built for Apple silicon only, and the Homebrew cask now requires it. On an Intel Mac, Pacenote stays at 0.5.6.

After you upgrade

Restart Claude Code or Codex sessions you have open, so they get Pacenote's new update_task tool.
The first Collect now also fills in what older tasks lack (Code or Reply, the repository and the thread summed up), so it may take a little longer once.

Todo

Open tasks follow their thread. Each collection checks the open tasks' threads, as it does to close them. When a thread changed one (a new due date, a sharper ask, the repository named, you now asked by name), it updates only what changed, and only on clear signs. Tasks you marked Done or Dismissed are left as they are, and a Maybe you kept stays a task.
A task that changed says Updated in the list, and its open row says what changed and why: "mina moved it to Wednesday".
The open row says less. The button tells a code task from a reply, without a chip. Each line has a name, a short note and one action (Continue). Click a session's name to read its log, or a run's request to open it in Runs.
A collection's detail in Runs lists the tasks it updated, and a task there opens its row in Todo.

AI tools

Pacenote's MCP server has a new tool, update_task, and task_context includes a task's recent changes.