AI Business OS
These notes cover every AI Business OS release up to 3.0.2, newest first. Each entry describes what changes for you in your workspace. The notes leave out changes that only affect how GenAI Skills Academy builds and maintains the product.
To bring your workspace up to date, run /update. Updating Your Installation explains how updates treat your own edits.
Released on 15 October 2026, this version keeps session history by calendar month, archives earlier months and shows validation warnings when you save or close a session.
- Session history by calendar month. The session history now holds the current calendar month, with no fixed size, where it used to keep 20 entries.
/saveand/nightrunarchive-history.sh, which moves every entry from an earlier month into the archive file for that month in.claude/state/history/, so no entry is dropped, as State Files and Validation describes. - Project session entries from
/night./nightnow adds a session entry to each project it updates, as/savealready did. - Warnings in the
/saveand/nightreports. When the validation script passes with warnings, both commands list every warning in full, and a clean run showsValidator: no warnings, as State Files and Validation describes.
Released on 14 October 2026, this version brings documentation and command fixes and leaves the layout of an existing workspace unchanged.
- Licence. The GenAI Skills Academy Software Licence now ships as a
LICENSEfile, and/updatedelivers it. - Platforms and support. The README now states that AI Business OS is built and tested on macOS, that Windows may work through WSL or Git Bash but is not directly supported, and that support is purchased separately.
- Engine health in
/status./statusnow runs a health check and adds an Engine Health section to its report. The check compares each critical engine file with the published copy of the version your workspace runs, so a normal update no longer shows up as a problem. - Warning before engine edits. Before Claude edits an engine file, it now tells you whether the change is blocked or will be merged on the next update.
- Project numbering follows your register.
/newprojectreads the project IDs already instate.jsonbefore it creates a new one. A new workspace starts atP001, and a workspace that already uses another format keeps it. If your register holds two formats,/newprojectstops and asks which to use. A re-run of/setupkeeps your existing numbering. - Fixes reach workspaces without PRIMA Project Management.
/day,/night,/setup,/status,/sync,/newproject,/resume,/dashboardand the state files and scripts were previously updated only on new installs./updatenow delivers fixes to them and keeps your edits by merging. With PRIMA Project Management installed, its own update still manages these files. - Undoing an update.
/update rollback, or asking Claude to undo the update, now restores the previous engine files, reports what was restored and commits the result. The rollback now restores every file in the backup. - Fewer false merge conflicts. Files you never edited no longer show conflicts after an update. This takes effect from the update after this one.
/savewithout PRIMA Project Management./saveno longer depends on a rule that only PRIMA Project Management installs.- One result for the old company profile. Both
/setupand/migrate-companynow archive an oldCLIENT_PROFILE.mdto.claude/engine-backups/company-migration/. - Calendar settings.
/setupnow writes calendar entries in the format the state schema expects. - Dashboard output ignored by git. The generated
Documentation/Reports/prima-dashboard.htmlis now listed in.gitignore. - Install instructions. The README and the getting started guide now describe installing from the prompt in the email you receive when you buy.
- Documentation corrections. Command tables now list every command that ships, the rules and documentation lists match the files, and the guides describe Windows support, permissions and project numbering as the code works.
Released on 15 September 2026, this version changes the default layout for new workspaces and leaves every existing workspace as it is.
- Domains for new installations. A new workspace now has a
Domains/folder with seventeen numbered domains, from01 Clientsto16 Legal & Complianceplus99 Cross-Domain. Each domain has its ownCLAUDE.mdand numbered reference subfolders, and tracked projects live inside the domain they belong to. See Domains. /newprojectand/newclientdetect your layout. WhereDomains/exists,/newprojectasks which domain the project belongs to and files it there, and/newclientcreates the client underDomains/01 Clients/. Where it does not, both commands work as they did in 2.x./dayand/statusread fromstate.json. Both now report every registered project wherever its folder sits, in a domain, a client folder or a folder of your own.AGENTS.mdfiles. Every domain folder and sample project carries anAGENTS.mdfile, and/newprojectwrites one beside each new project’sCLAUDE.md, so other AI coding tools read the same project rules.- More recommended VS Code extensions. VS Code now offers OpenAI Codex, Ollama and Live Preview alongside Claude Code and Bearded Icons when you first open the workspace.
- Six skills leave the template.
copywriting,search-engine-optimisation,email-drafting,creating-presentations,processing-spreadsheetsandprocessing-documentsno longer ship. They are available as skill packs in the GenAI Skills Academy community, and a workspace that already has them keeps them. /updatekeeps your edits more reliably. The three-way merge now uses the published copy of the version you last received as its base, so an edit you made before an earlier update is no longer lost when the same section changes upstream./updatefinishes cleanly. The update script no longer ends with an error after replacing itself during the run.- Community link. The README now links to the GenAI Skills Academy learning community.
A maintenance release on 2 September 2026 with a change to .gitignore.
Released on 17 August 2026, this version closes two ways an update could lose your changes.
- Your settings survive updates.
/updateused to replace.claude/settings.jsonin full, losing the tool approvals and hooks you had added. It now merges the engine’s entries with yours. - First update on a customised workspace. The first update overwrote files you had changed, without notice. They are now listed as “no merge base” in the preview and after the update, with the backup path for recovery.
Released 17 August 2026.
AGENTS.mdat the workspace root. Other AI coding tools, such as Codex, Cursor, Gemini CLI and Copilot, readAGENTS.mdand now find pointers to the workspace rules there.CLAUDE.mdremains the main file.- A script to add
AGENTS.mdto existing folders.Infrastructure/Scripts/backfill-project-agents-stubs.shwrites a pointer file into every project and client folder that has aCLAUDE.md. - Agent-agnostic design guide. A new document in
.claude/docs/explains how the workspace stays usable with tools other than Claude Code.
Released on 17 July 2026, this version fixes /update under Git Bash on Windows.
- The update script now handles the line endings that Windows builds of
jqproduce, stops Git Bash from rewriting its arguments, and connects to the upstream template over HTTPS, which works on machines without SSH keys.
Released 9 June 2026.
- Decomposition rule. A new rule helps Claude decide whether a repeated task should be a single tool call, a script, a skill or an agent, and pick the simplest one that fits.
Released 21 May 2026.
/migrate-company. A new command converts an old single-fileCLIENT_PROFILE.mdinto the six files in.claude/company/, then walks you through any areas that need more detail.- Prompt after updating. When an update finds an old
CLIENT_PROFILE.md, it now tells you to run the migration.
Released 21 May 2026.
- No repeated permission questions. A new rule tells Claude that a direct instruction from you is the permission, so it does not ask again before internal workspace actions.
/resumeby time./resumenow accepts a time such as15:40to find a specific checkpoint./savereconciliation./savenow follows the same task reconciliation steps as the end-of-session routine.
Released on 10 April 2026, this version changes where your company information lives.
- Company context files. Six files in
.claude/company/replace the singleCLIENT_PROFILE.md, covering overview, team, audiences, voice, brand and industry./setupwalks you through them. Existing workspaces need to move their company details into the new files. - Placeholder names changed. Placeholders in
CLAUDE.mdnow read[COMPANY_NAME],[companyname]and[CLOUD_STORAGE_PATH]. - Safety hooks. Two checks now run before Claude acts. One blocks edits to critical engine files, and the other blocks dangerous commands such as forced deletion, force push and
sudo. - Three kinds of engine file. Engine files are now classed as critical, customisable or standard, and customisable files keep your edits through a three-way merge on update.
- Seven new skills. The template gains skills for copywriting, creating presentations, processing spreadsheets, processing documents, documenting workflows, search engine optimisation and email drafting.
- Product list. The README gains a table of the PRIMA products.
An update to /newclient, released on 17 March 2026.
A maintenance release on 17 March 2026 with a change to .gitignore.
Released 13 March 2026.
/updateno longer fails when a list of files it works through is empty.
Released 11 March 2026.
- Cloud sync warning. A new guide explains why your workspace should not sit inside Dropbox, OneDrive, Google Drive or iCloud Drive.
Released 11 March 2026.
/save. A new command saves your session mid-way and gives you a reference to resume from.
Documentation updates, released on 28 February 2026.
Released 28 February 2026.
- Engine protection. Critical engine files are now marked and protected, and Claude is told to put your changes in a companion file and leave the critical file as it is.
- Engine health in
/status./statuschecks whether critical files have changed. - Merging on update. During
/update, engine files you have changed are now merged with the new version. Where both sides changed the same lines, the file is marked for you to resolve. - PRIMA Project Management updates through
/update. One command now checks for and applies both engine and PRIMA Project Management updates, and the dry run previews both. - Windows guidance. The README and getting started guide now describe the WSL requirement for Windows.
Updates to /newclient and the state validation script, released on 27 February 2026.
Released 27 February 2026.
- Department folders. Finance, Legal, Marketing, Operations, Products and Sales folders now each carry their own
CLAUDE.md.
Documentation updates and a change to .gitignore, released on 27 February 2026.
Documentation updates, released on 26 February 2026.
Documentation updates, released on 26 February 2026.
Released 26 February 2026.
- Rules and skills in
/newproject. The project wizard now asks which rules and skills belong to the new project, detects the ones that already exist and marks new ones to be created.
Released 25 February 2026.
processing-pdfsskill. Extracts text from PDF files, merges, splits, fills forms and adds annotations.- PDF size scale. A five-level scale makes Claude check a PDF’s size and page count before reading it, and switches to chunked or parallel reading for large files.
Released on 24 February 2026, this version added the extension pack installer’s command file and updated the guides that describe it.
Released on 24 February 2026, this version added an installer for extension packs, which the current documentation does not cover.
Released 23 February 2026.
- The version badge in the README now updates automatically.
Released 23 February 2026.
- Automatic version tracking. A commit hook now adds new engine files to the engine manifest and raises the version number to match.
Released on 23 February 2026, this version introduced the update system.
/update. Checks for and applies engine updates from the upstream template. Your own files, such asCLAUDE.md,state.jsonandintegrations.json, are never touched.- Backups and rollback. Every update saves a backup to
.claude/engine-backups/, with a dry run to preview changes and a rollback to undo them. - Engine version in
/status. - PRIMA detection. Updates skip the files PRIMA Project Management manages when it is installed.