v0.5.23

Pace uses Pacenote's own tools when it answers in the built-in sandbox: ask it in a thread to keep what you need to do,
and it is in your Todo.

brew update && brew upgrade --cask pacenote

The upgrade quits the running app first; open Pacenote again if it does not come back on its own. Claude Code and Codex
sessions already open keep the previous Pacenote tools until they start again.

Pace in Slack

• Keeps tasks for you. "Keep the reviews here as tasks" adds them to Todo, from Pace, each linking to your request
  in the thread. The same title still open there is kept once. A request for tasks goes to Todo unless you name Jira or
  another tracker.
• Knows your list, your work and your recaps. What is on your list, the retry review is done, what did I do this
  week: Pace reads and closes your tasks, and reads where you contribute and your recaps, as your AI tools do.
• Picks up from what it said there. Its earlier answers in the same channel, when the run history is kept.
• Only for you, and fit for the channel. The tools act for the person Pace answers, as Pacenote says, never as the
  model says. Tasks from DMs are left out, and earlier answers come only from the channel they were posted in.
• On this Mac. The tools run in Pace, not in the VM, which never sees Pacenote's files and needs no new image. They
  answer while Todo is on. When answers run on this Mac without the sandbox, Pace does not have them yet.