Configuration

App Settings

The desktop app settings include:

• review provider;
• tracked repositories;
• local clone paths;
• provider credentials;
• default diff view;
• AI provider, model, and effort;
• preferred terminal for review and fix flows;
• Jira and Notion context integration tokens;
• automatic sync interval;
• menu bar sync and notifications.

Repository Config

Norn can read .norn.yaml from a configured local repository.

version: "0.1"
review:
  profile: frontend-strict
  mode: balanced
  prompt:
    replace: |
      Full repository-owned review prompt.
  findings:
    minSeverity: low
profiles:
  frontend-strict:
    mode: strict
    minSeverity: medium
    policyPacks:
      - ./norn-policies/react-saas
    analyzers:
      tsc: required
paths:
  include:
    - "src/**"
  exclude:
    - "dist/**"
policy:
  packs:
    - ./norn-policies/agentic-code
  rules:
    - id: no-cross-module-imports
      severity: medium
      instruction: "Flag imports that cross module ownership boundaries."
publish:
  defaultMode: inline
  requireManualSubmit: true

Policy packs can contribute prompt extensions, rules, path rules, profiles, and analyzer defaults from local directories. Profiles can be selected from the desktop AI review panel per run. Repo config and policy packs should not contain credentials, tokens, private URLs, or other secrets.

If a repository does not have .norn.yaml, Norn also reads a .norn/ folder. system-prompt.md, review-prompt.md, review.md, or prompt.md replace the built-in review prompt, and packs/*/pack.yaml entries are loaded as local policy packs. When both roots exist, Norn rejects the configuration and asks the maintainer to keep exactly one.

During the compatibility window, .lachesi.yaml, .lachesi/, and .lachesi.local.yaml remain fallback-only inputs. Norn rejects mixed old/new repository roots instead of merging them. Preview a safe migration with norn config migrate --dry-run; omit --dry-run to execute it without overwriting an existing canonical target.

The repository includes a loadable prototype pack at examples/policy-packs/agentic-code. Use it as a local-path example for agentic-code review rules, named profiles, analyzer defaults, and structured output samples.

Validate repo config locally before running a review:

norn config validate --repo-path . --format json

The command exits with code 2 when the config is invalid.