Harness reference
Where each supported tool keeps its hook configuration, as Lore writes it. This table is generated from the Lore CLI’s own definitions, so it always matches what lore hooks install does.
| Tool | User (under your home) | Repository | Admin-managed | Managed-only switch |
|---|---|---|---|---|
| Claude Code | ~/.claude/settings.json | .claude/settings.json | macOS: /Library/Application Support/ClaudeCode/managed-settings.d/lore-hooks.jsonLinux: /etc/claude-code/managed-settings.d/lore-hooks.jsonWindows: C:\Program Files\ClaudeCode\managed-settings.d\lore-hooks.json | allowManagedHooksOnly = true |
| OpenAI Codex | ~/.codex/hooks.json | .codex/hooks.json | macOS: /etc/codex/requirements.tomlLinux: /etc/codex/requirements.tomlWindows: C:\ProgramData\OpenAI\Codex\requirements.toml | allow_managed_hooks_only = true |
| GitHub Copilot | ~/.copilot/hooks/lore.json | .github/hooks/lore.json | macOS: /etc/github-copilot/policy.d/lore.jsonLinux: /etc/github-copilot/policy.d/lore.jsonWindows: C:\ProgramData\GitHub\Copilot\policy.d\lore.json | allowManagedHooksOnly = trueset in Copilot managed-settings.json (/Library/Application Support/GitHubCopilot/, /etc/github-copilot/, %ProgramFiles%\GitHubCopilot\) |
| Cursor | ~/.cursor/hooks.json | .cursor/hooks.json | macOS: /Library/Application Support/Cursor/hooks.jsonLinux: /etc/cursor/hooks.jsonWindows: C:\ProgramData\Cursor\hooks.json | none |
Lore’s entry has a 10-second timeout in every tool. That is well above the hook’s own 3-second limit, so the tool never cuts it off before it has fallen back to the cache.
Per tool
- Claude Code. In managed scope, Lore writes its own drop-in file in
managed-settings.d/, which merges with your org’smanaged-settings.jsonwithout changing it. Claude Code applies only its highest-priority managed source, though: claude.ai’s managed settings, then an MDM profile or registry policy, then files. If your org already uses one of the higher ones, set"managedSourcesBehavior": "merge"there, or put the hook there. - OpenAI Codex. Codex keeps managed hooks inside
requirements.toml. Lore edits only its own marked block in that file, and refuses (pointing you to a manual merge) if the file already defines its own[hooks]table. Hooks outside managed scope need approval in/hooks. - GitHub Copilot. Lore writes its own
lore.jsonin each hooks directory. Copilot’s “only managed hooks” policy (allowManagedHooksOnly) lives in Copilot’s managed settings, which Lore doesn’t write. - Cursor. Cursor has no “only managed hooks” switch. By default Cursor also runs Claude Code’s hooks; Lore detects this and delivers once.