Every morning my briefing says "A newer version (2026.07.04) is available. Say update" but my folder says 2026.09.16

Modified on Sun, 11 Oct at 7:20 AM

No, you are not behind, and saying update will not change anything. If your _config/version file reads 2026.09.16, you already have the newest published playbook for both Pearl and Otto: the 2026.07.04 line comes from an old copy of the morning script on your computer, not from a real new version.

Where the line comes from

If you set up Otto's Autopilot from the terminal, your computer starts a small script every morning to run the sweep. It lives in your BookingHQ folder: scripts/run-agent.sh on a Mac, started by launchd, or scripts/run-agent.ps1 on Windows, started by Task Scheduler. Before the sweep, the script checks for a new version and, when it thinks there is one, tells Otto to open the briefing with a line like this:

A newer version (2026.07.04) is available. Say "update booked solid" to get what's new.

A copy of the script from before 18 July checks the wrong place. It asks an old address that was retired in July and still answers 2026.07.04, and it raises the line whenever that number differs from yours, even when yours is newer. So a 2026.09.16 folder hears about 2026.07.04 every morning. If the finished briefing does not mention 2026.07.04, the script adds the line to the end itself as an "Otto note".

Copies from 18 July on read your own line and only speak up when the published number is really newer than yours.

Should I say update?

It does no harm, and it does not help here. When you say update booked solid, click Check for updates in the top bar, or run booked update in the terminal, your folder is compared with your own line on the published list. Both read 2026.09.16, so no new playbook is downloaded and nothing in your folder changes. In the app, the update window says Your BookingHQ playbook is current (2026.09.16).

An update also leaves the morning script alone. It refreshes the playbook and AUTOPILOT.md, and keeps the script, your schedule, the queue and the Booth as they are, so the line is back the next morning.

Booked Solid 1.11.100 (25 September) added a step meant to swap this old script out during a playbook refresh, but that step does not reach a folder that is already current, and there is no newer script for it to swap in yet. So do not wait on an update for this one.

How to make it stop

Email us and say that your morning briefing names 2026.07.04. We will help you replace the old script with the current one. Do not ask Otto to rewrite it: its update guide tells it never to write the morning script from memory.

Until then the line is harmless and you can ignore it.

Check your versions yourself

  • Your playbook: open _config/version in your BookingHQ folder. As of 27 September, 2026.09.16 is the newest published playbook for Pearl and Otto.
  • Your app: the number sits at the very bottom of the left sidebar, as Booked Solid followed by the version. Click it to check for updates.

For which version line is yours, and why the workspace check also prints 2026.07.04, see Which version line is mine? Pearl reads pro, Otto reads autopilot.

Prefer a fully managed experience? Booked Solid OS runs on your computer and you stay hands-on. If you would rather have this handled for you on a hosted platform (lead finding, follow-ups, email sending, invoicing, all managed in one place), take a look at KM Hub from the same team.

Still stuck? Email bookedsolid@kivimedia.freshdesk.com and a person will help.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article