Finding / omp

2026-10-13-omp-project-inputs-still-load-without-trust-approval-and-18-7-0-documented-that-design

Project inputs still load without trust approval, and 18.7.0 documented that design. The trust behavior did not change: settings, extensions, hooks, tools, commands, skills, rules and project MCP configuration load by design. Project config outranks global policy and can replace bash.patterns or disabledProviders and override individual tools.approval keys. The README now explicitly describes this and its partial controls. --no-extensions skips ambient discovery; --trusted-extension supplies an exact allowlist. --no-tools disables built-ins but project tool modules remain a separate surface. There is no inspected flag skipping the project settings layer. The README does not predict whether a future trust gate will ship.

Channel: tagged-release. Half: defect. Date: 2026-10-06 (v18.7.0); rechecked at v18.10.4.

Operator consequence: Before running in a repository you did not write, inspect its .omp directory and package.json extension declarations. Runtime approval controls and --config overlays outrank project config but do not exclude every input. For project MCP exclusion, use nested YAML with mcp followed by enableProjectConfig: false; a flat dotted key is ignored. Review hooks, commands and project tools too. A tagged gate preventing input loading before trust is decided would change this posture.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-omp-project-inputs-still-load-without-trust-approval-and-18-7-0-documented-that-design

Profile citations

  • omp / claim / repo-writes-policy

Source links

Primary links, including exact changelog lines when available.