Update Issues
How do I know an update is available?
Section titled “How do I know an update is available?”Compare the version in your FRAMEWORK_VERSION file against the current version at the repository. Different means an update exists.
Will updating erase my work?
Section titled “Will updating erase my work?”No. The update command only touches framework files: the thinking process skills, diagnostic methodology, change sequence, system manifest, the critic agent and agent documentation, the session summary template, README, and LICENSE.
Your context files, pipeline, processes, diagnostics, decisions, CLAUDE.md, soul.md, communication-style.md, custom skills, and custom sub-agents are never touched.
The complete list is in FRAMEWORK_FILES.md inside your own system.
How do I update?
Section titled “How do I update?”Easiest: tell Claude Code “Update the base framework from the upstream repository.”
Or run it yourself:
git fetch upstreamgit checkout upstream/main -- .claude/skills/ .claude/rules/ .claude/agents/ .claude/settings.json templates/session-summary.md README.md LICENSE FRAMEWORK_VERSION FRAMEWORK_FILES.md .gitignoregit add -Agit commit -m "Updated framework"See Updating the Framework for what each part does.
I have not set up the upstream remote
Section titled “I have not set up the upstream remote”Run this once:
git remote add upstream https://github.com/lesixcompanies/90mm-real-estate-bos.gitThen you can pull updates any time.
The update gives me a merge conflict
Section titled “The update gives me a merge conflict”This usually means you edited a framework file directly.
The safest fix is to tell Claude Code which version to keep. For framework files, keep upstream. For CLAUDE.md — which should not be in the update path at all — keep yours.