Troubleshooting
Start with:
lore hooks statusFor each tool it shows whether the tool was detected, where Lore’s hook is installed (user, project or managed scope) and for which org, the last delivery, and how old the cached context is. lore hooks status --json gives the same data in machine-readable form.
Status fields
| Field | Meaning |
|---|---|
detected | The tool’s settings folder exists in your home directory |
| scope lines | Each place a Lore hook is installed, with its org and mode |
here: org … | The org a session started in the current directory gets, and where it comes from. Lines below it name the hooks that stay silent, and an ignored .lore.yaml (see When several Lore hooks are installed) |
last delivery: fresh | The last session received context straight from Lore |
last delivery: cached | Lore couldn’t be reached, so the session got the cached copy |
last delivery: notice | The session got a one-line notice instead of context (see below) |
cached context … old | Age of the newest cached context for that org |
sign-in | valid, refreshable (expired; the next session refreshes it in the background), expired (run lore login) or missing |
last refresh | The last session refresh: refreshed, rejected (run lore login), unavailable (the identity provider couldn’t be reached) or no-session |
lore auth status shows your session’s expiry and the last refresh with its cause. Detailed diagnostics, including each background refresh, are in ~/.config/lore/logs/hooks.log. The hook never writes errors into your AI tool.
Notices in the session
| Notice | Fix |
|---|---|
| not signed in | Run lore login |
| your session expired | Run lore login |
| refreshing your sign-in | Nothing to do: the session is being renewed in the background, and the next session gets your org’s context |
| …isn’t a member of the org | Check the org in lore hooks status, or ask an org owner to add you. Cached context is deliberately not shown |
| there is no org … | The org in the hook, or in the repository’s .lore.yaml, doesn’t exist. Fix the name there, or run lore hooks pin --org=<org> |
| …named by this repository’s .lore.yaml | The repository is bound to an org you don’t belong to. Ask that org’s owner for access. Lore doesn’t deliver your other org there instead |
| no org configured for this hook | Reinstall with lore hooks install --org=<your-org> |
| couldn’t reach the Registry and there is no recent cached context | Check your network. Context comes back at the next session |
| …needs a Pro plan, which your org no longer has | Ask an org owner. Org-mode hooks require Pro |
Common problems
- The context of the wrong org, or of two orgs. Run
lore hooks statusin the repository: thehere:lines show which hooks answer. Two answers mean the repository has a hook Lore can’t confirm runs for you (Codex, Cursor); use.lore.yamlinstead, or align the hooks’ orgs. - No context and no notice. Start a new session, because hooks run at session start. In Codex, check that you approved the hook in
/hooks. In Cursor, try a second message (see Individual mode). - The context arrives twice. Update the Lore CLI. Current versions deliver once even when a tool runs several tools’ hook files.
installskipped a file. The existing file isn’t valid JSON (or, for Codex managed scope, already defines[hooks]). Lore never overwrites a file it can’t parse. Fix the file, then run the command again.- Memory is missing but Rules appear. Org memory requires a Pro plan. Rules are delivered on every plan.