Pacenote v0.4.1

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

Collecting with your AI tool's Slack connector

Pacenote no longer reads Slack with a user token of its own. The tool you already use reads it with its own Slack access and adds your tasks through Pacenote's MCP server, so there are no Slack app scopes to add, no reinstall and no token to copy.

• Turn on Settings > Tasks > Let AI tools add my tasks. DMs and channels to leave out are set there too, and apply at once.
• In Claude Code, run /mcp__pacenote__collect_tasks; the Tasks screen copies the command. In Codex, ask it to collect your tasks with Pacenote's collect_context tool.
• New MCP tools: collect_context (the rules, what to leave out, since when, the open tasks), add_tasks and close_task. add_tasks keeps your settings whatever the tool sends: channels left out, and DMs while they do not count, are skipped.
• The list works as before: precision first with Maybe, Done and Dismiss with reasons, closing by itself, the dismiss rate.

If you saved a User OAuth Token in 0.4.0, it is no longer used: you can remove the user scopes from your Slack app and the SLACK_USER_TOKEN line from the settings file.

Adding Pacenote to Claude Code and Codex

Settings > Tasks, and Settings > History & logs while the history is shared, list Claude Code and Codex: whether each has Pacenote's MCP server and reaches it, with one button. Add registers this app's server with the tool's own CLI, Use this app replaces one from a moved app or a dev build, and Remove takes it out. For Codex, Pacenote starts the server Codex has registered and lists its tools, since Codex has no check of its own. The commands to do it by hand are still under Add it by hand. Your tasks from Slack has the steps.