ConfigResolutionError

Reason category — callers translate this into UI text or exit codes.

Plain-text description suitable for direct display to the user.

Project-level configs with server entries skipped by the trust gate.

Populated when at least one discovered project config had server entries skipped during auto-discovery (unapproved, disabled, or because the user's trust policy could not be read), regardless of kind. Callers can surface a "skipping untrusted project servers" hint alongside the primary error.

Names found in a legacy [mcp].enabled_project_servers list, sorted.

Mirrors resolve_and_load_mcp_tools: non-empty means the user relied on the removed flat allowlist, so those servers silently stopped loading. Callers should surface the migration hint so this non-interactive path explains the change instead of the servers just vanishing.

Set when the user's trust policy (config.toml) could not be read.

When non-None, project servers were dropped because the policy failed to load — not because they were unapproved — so callers should surface this reason instead of the misleading untrusted_project_paths notice. On this error type message already embeds it; callers use the field only to suppress the misleading untrusted notice.

True when the removed DEEPAGENTS_CODE_ENABLED_PROJECT_MCP_SERVERS env var is set. Twin of legacy_ignored for the env surface; see format_legacy_env_ignored_notice.

Count of persisted [mcp].enabled_project_server_approvals rows dropped as malformed. Non-zero means a saved approval could not be read, so its server silently stopped pre-approving; surfaced for parity with legacy_ignored. See format_malformed_approvals_notice.