Skip to content

Troubleshooting

Installation

npx create-lore fails with "Could not find remote branch"

The installer clones a specific version tag from GitHub. If the tag doesn't exist, the clone fails with an error like:

fatal: Remote branch vX.Y.Z not found in upstream origin

Fix: Update to the latest version of create-lore:

npx create-lore@latest my-project

If the problem persists, open an issue.

npx create-lore fails with a network error

fatal: unable to access 'https://github.com/lorehq/lore.git/': Could not resolve host: github.com

Fix: Check your internet connection and DNS. The installer needs to reach github.com to clone the template. Firewalls, VPNs, and corporate proxies can block git access.

Node version errors

Lore requires Node.js 18 or later.

node --version  # must be >= 18

Hooks

Hooks aren't firing

Claude Code: Check that .lore/hooks/ exists and contains .js files. Run claude from the project root.

Cursor: Check that .cursor/hooks.json exists and references files in .cursor/hooks/. Open the project folder directly in Cursor (not a parent directory).

OpenCode: Check that opencode.json exists and .opencode/plugins/ contains .js files.

For all platforms, verify with:

bash .lore/scripts/validate-consistency.sh

"MEMORY.md is intercepted" warning

Lore blocks MEMORY.md to prevent platform-level memory from overwriting knowledge; route persistent knowledge to skills or docs instead. See Production Readiness: MEMORY.md Protection for details and alternatives.

Escalating capture reminders are too aggressive

Adjust nudgeThreshold and warnThreshold in .lore/config.json. See Configuration: Hook Profile for profile options.

Worker Tiers

All workers run on the same model (not their configured tier)

Worker agents inherit the orchestrator's model when Claude Code ignores the model: field in their agent frontmatter. This happens in two scenarios:

Scenario 1 — Using a cloud deployment (Foundry, Bedrock, Vertex): Claude Code resolves short aliases (haiku, sonnet, opus) through ANTHROPIC_DEFAULT_*_MODEL env vars. If those vars aren't set, it falls back to its own hardcoded model IDs. Set all three in ~/.claude/settings.json:

{
  "env": {
    "ANTHROPIC_DEFAULT_HAIKU_MODEL": "your-haiku-deployment",
    "ANTHROPIC_DEFAULT_SONNET_MODEL": "your-sonnet-deployment",
    "ANTHROPIC_DEFAULT_OPUS_MODEL": "your-opus-deployment"
  }
}

Scenario 2 — Full deployment names in config: If subagentDefaults.claude contains full model IDs (e.g. claude-opus-4-6) instead of short aliases, Claude Code ignores the generated frontmatter value and workers inherit the orchestrator's model. Lore's generate-agents.js correctly stamps short aliases into .claude/agents/ frontmatter regardless — but if you are on an older version, run /lore-update to get the fix.

Verify the generated agents look correct:

grep "^model:" .claude/agents/lore-worker*.md
# Should show: model: haiku / model: sonnet / model: opus

opus tier returns a 404 deployment error

Claude Code maps opus → its internal default opus model ID, which may not exist in your deployment. Fix: set ANTHROPIC_DEFAULT_OPUS_MODEL in ~/.claude/settings.json to match your deployed model name. Restart Claude Code after changing settings.

Consistency

validate-consistency.sh fails

This script runs 11 cross-reference checks. Common failures:

Failure Fix
Platform copies out of sync bash .lore/scripts/sync-platform-skills.sh
Registry stale bash .lore/scripts/generate-registries.sh
Nav stale bash .lore/scripts/generate-nav.sh — regenerates mkdocs.yml nav after adding or renaming docs
Instructions out of sync bash .lore/scripts/sync-framework.sh (via /lore-update)

Updates

/lore-update shows conflicts

/lore-update only touches framework-owned files (lore-* prefix). If you see conflicts, you may have modified a lore-* file directly. Framework files are overwritten on sync — move your changes to an operator-owned file (no lore- prefix).

Version mismatch after update

Check that .lore/config.json and package.json agree:

bash .lore/scripts/check-version-sync.sh

If they diverge, the update didn't complete cleanly. Run /lore-update again.

Still Stuck?