Skip to Content
V1GovernanceIndividual mode

Individual mode

Each member installs the hook for the AI tools on their own machine. It works on every plan and takes about a minute.

Install the Lore CLI

# macOS / Linux curl -fsSL https://lore.infraestrutura.app/install.sh | sh
# Windows (PowerShell) irm https://lore.infraestrutura.app/install.ps1 | iex

Sign in

lore login

The hook uses this sign-in to fetch your org’s context, and refreshes it silently.

Install the hooks

lore hooks install --org=<your-org>

Lore detects which supported tools you use (Claude Code, Codex, GitHub Copilot, Cursor) and adds its session-start hook to each one’s user settings. Everything else in those files, including your own hooks, is left untouched. Running it again changes nothing.

  • --harness=claude,cursor limits it to some tools.
  • --dry-run prints the resulting files without writing them.
  • If you belong to a single org, you can leave out --org.

Check

lore hooks status

Then start a new session in your AI tool and ask it which org Rules it sees.

Tool-specific notes

  • Codex asks you to review new hooks before running them. Open Codex, run /hooks, and approve Lore’s hook. If the hook changes (for example after lore hooks install --org=<another-org>), Codex asks again. Until you approve it, Codex runs no hook and shows no warning, and lore hooks status lists no delivery for Codex.
  • Cursor can miss the context on the very first message of a new chat, a known Cursor issue. It’s there from the next message on.
  • GitHub Copilot: the hook works in Copilot CLI and in VS Code when the chat session uses the Copilot agent.
  • Claude Code in interactive mode runs hooks after you trust the folder.

Several tools also run each other’s hook files. Cursor, for example, runs Claude Code’s hooks by default, and Copilot CLI and VS Code’s Copilot agent run a repository’s .claude/settings.json. Lore detects which tool is actually running and makes sure your context arrives once, in the right format.

Settings

VariableDefaultEffect
LORE_HOOK_TIMEOUT3sHow long the hook may take before falling back to the cache
LORE_HOOK_CONTEXT_BUDGET_BYTES8000Maximum size of the context left for memory after the Rules. Memory never takes space from the Rules
LORE_HOOK_RULES_CEILING_BYTES8000Maximum size of the Rules part. Every Rule is always named; Rules whose full text doesn’t fit are shown as a line pointing to it, and lore hooks status says how many
LORE_ORGnoneDefault org when --org is omitted

Update or remove

  • Switching orgs: run lore hooks install --org=<other-org>. It replaces Lore’s entry.
  • Removing: run lore hooks uninstall. It removes only Lore’s entries.
© 2025 Lore · Built by M1 Cloud