ai-project-bootstrap
v1.0.0
Signed out
Some pages show more once you sign in — your licence key, your usage, and what the subscription covers.
Getting started
What this isInstallationThe wizard, question by questionYour first project
Choosing a stack
Describing your idea (Pro)Licensing & open sourcePresetsArchetypesPreset or archetype?Cost estimation
Technology catalogue
Browse all 35 modulesCategories & selection rulesSupabase
CLI reference
generateaddimplementreviewanalyzeupgradedoctorGlobal flags & exit codes
The generated project
File-by-file contractAI rules per toolRegenerating safelyai-project.config.json
Contributing
Adding a technologyAdding an implement providerAdding an archetypeAdding pricing dataChanging the engine
Docs / CLI reference / upgrade

upgrade

add brings in something new. upgrade refreshes what is already there, using the exact selection the project was generated with.

cd my-app
npx ai-project-bootstrap upgrade
npx ai-project-bootstrap upgrade --dry-run
npx ai-project-bootstrap upgrade --dir ../my-app

What it reports

→How many files were added, how many updated, and how many were already current.
→Which newly-supported AI tools this project never opted into — it says so without adding them itself.
→Nothing is added to or removed from the stack. That is what add is for.

Opting into a new AI tool

Edit the aiTools array in ai-project.config.json and upgrade again. A config saved before that question existed has no aiTools key at all, which is treated as Cursor plus Claude Code — the original behaviour — not as 'nothing selected'.

It never touches a hand-edited file

The same fingerprint comparison add uses: unchanged since generation means safe to overwrite; changed means left alone, always.

Previous
analyze
Next
doctor
On this page
What it reportsOpting into a new AI tool
Source: README.md — Upgrading a project