Pacenote v0.5.9

Code tasks open where you work. A task with no folder yet suggests the folders you worked in lately, and collections can tell which repository a thread means without a link.

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.

After you upgrade

Restart Claude Code or Codex sessions you have open, so collections you run from them get your repositories too.

Continuing work

Folders you worked in, suggested. When a task's repository has no folder yet, or the task has none, the folder dialog lists the folders you worked in with Claude Code or Codex in the last 30 days, with when you last did. The likeliest one is already chosen: for a repository, its checkouts you worked in; for a task with no repository, the folder its title or summary names, then its channel. Pacenote reads only each session's folder from the tools' own logs on this Mac.
Where it opens, on hover. A task whose repository has a folder still opens without asking; its Continue button now shows that folder on hover. Continue in another folder under the row's ⋯ opens it somewhere else.
Choose another folder starts next to the folder you worked in last, not your home folder.

Todo

Collections know your repositories. A collection is given the names of the repositories you work in (the ones with a folder, and those of the folders you worked in lately), never where they are. When a thread plainly means one of them, the task gets it without a pull request link, and an open task with no repository gets one filled in.

AI tools

collect_context lists the repositories you work in as repos, by name only.