Pacenote v0.4.7

Pace keeps going when something goes wrong, and tells you when it can't. On this Mac it reads less, and what it posts is checked for secrets first.

brew update && brew upgrade --cask pacenote

The upgrade quits the running app first and reopens it. The bot gets up to 15 seconds to finish its requests; the rest stop and resume on the next start. Config and run history are untouched.

Before you upgrade

With your own Slack app, Pace now needs to know who may ask: your Slack member ID in Settings > Messengers > Slack, or anyone in the workspace (MENTION_ALLOWED_USERS, or MENTION_ANYONE=on). Until then it shows Setup needed with the way there. Through the team hub nothing changes.
On this Mac, codex needs 0.138 or later, and Pace's runs no longer load your ~/.codex/config.toml: Pacenote passes the model and reasoning effort from its own settings.

Pace keeps going

A stop leaves nothing behind. Requests in progress get 15 seconds; then their reasoner runs stop (the CLI and whatever it started, or the container), and they resume on the next start without counting as a retry.
Mentions waiting their turn get 👀 at once, and a restart picks them up.
An answer is never posted twice: once posting begins, a restart does not answer again. One cut off partway gets ⚠️ and a word to the asker alone.
A bot.json left behind by a crash or a power cut no longer shows Pace as running elsewhere.
When Pace exits on its own, the app starts it again after 3 seconds, then 6, 12 and so on up to 5 minutes, where it used to give up after a few tries. The Pace screen counts down, with Start now and Stop.

The app

Open Pacenote when you log in (Settings > General): it opens in the menu bar without a window, and starts Pace if Start Pace when the app opens is on.
A notification when Pace needs attention while the window is closed: it stopped, it needs setup, it lost Slack for 2 minutes or more, or it cannot answer (a rejected sign-in, a usage limit, the sandbox's proxy). Clicking it opens the screen to look at, and the menu bar shows ⚠︎ while it lasts.
When a newer Pacenote is out, the status bar says Update, and Settings > General has the brew command and the release notes. The app looks twice a day; PACENOTE_DESKTOP_UPDATE_CHECK=off turns that off.
Copy diagnostics (Settings > General > Help) gathers versions, Pace's status, the settings without their secrets and the latest logs for a bug report.
A window whose process ends loads again, and a screen that fails shows Reload instead of going blank.
Pace's mark turns while Pace is connected, four times as fast while it answers; stopped, a gray stop sign stands in for it.

Safer on this Mac

Answers are checked before they are posted: the secrets Pacenote holds and the common token formats are taken out, and the run notes how many.
claude reads only the reference directory, and codex runs under its own permission profile. Neither reads .env files, Pacenote's folders or the usual credential folders, and the CLIs no longer get Pacenote's tokens.
~/.pacenote is kept to your account (700, and .env 600).
Pace checks that the CLI is installed, signed in and new enough, at start and every 5 minutes, and says what to do in the status bar.
People from another organization in a Slack Connect channel are told Pace answers only its own workspace.
Settings > Messengers > Slack: Create the Slack app opens Slack with Pacenote's manifest filled in.