News › Release
Pacenote v0.5.16
Todo follows your work into the Claude Code and Codex sessions you start yourself: a session continued after /clear, in a new terminal or a worktree stays with its task, and one that only looks related is offered for you to link.
brew update && brew upgrade --cask pacenoteThe upgrade quits the running app first and reopens it, once. To have Todo find your own sessions, turn on Settings > Todo > "Show sessions you start yourself"; it stays off until you do.
Your own sessions
- Linked by themselves. A session joins a task's work log when it used Pacenote's task tools for the task, when what you typed has the task's Slack link, or when it worked on the task's branch in its repository: a branch other than the default one that a session already in its log worked on. A branch two tasks share links neither.
- Suggested when they only look related. A session in the task's repository, active since the task was posted, that shares its words (a PR number, an issue key, a file or code name, words of its title) shows as "Looks related" in the open task. Link adds it; Not it is not asked again. Its log opens like any other session's.
- Where it stands, on the row. An open task's row says when its latest session was last active ("Claude Code 5m ago"), and a session's line names the branch it is on.
- Read on this Mac, kept short. Claude Code's logs (the CLI, the Claude app and IDE extensions) and Codex's, of the last two weeks, are read where they left off, about every 30 seconds while Todo is open. Only a session's id, folder and branch are kept; what was said stays in the tool's log, and nothing from the logs leaves this Mac. Pacenote's own sessions and temporary folders are left out.