Local-Only Mode - AI Blueprint Docs

Keep Blueprint workflow state out of the remote repository when portability is not desired.

Choose during onboarding

Onboarding asks whether Blueprint workflow files should be committed or kept local. Committing them gives collaborators and future machines the same context. Local-only mode keeps that state on one checkout.

What to ignore

Local-only mode adds the Blueprint workflow paths to .gitignore:

# AI Blueprint local workflow files
.agents/
.claude/
blueprint/
CLAUDE.md

AGENTS.md stays tracked as the lightweight public project guide for commands and conventions.

Ignoring blueprint/ also keeps the installed version and managed-file baseline in blueprint/.state/ local to this checkout. In committed mode, keep blueprint/.state/manifest.json tracked while its nested .gitignore excludes backups and staging files.

Tradeoffs

Committed workflow	Local-only workflow
Portable context and shared history	No workflow files in the remote repository
Reviewable changes to plans and standards	Each checkout needs separate setup
Easier cross-tool and cross-machine continuation	History can disappear with the working copy

Local-only mode changes storage, not safety. Commit, merge, push, deployment, and external-action boundaries still apply.