Inspector, Settings

Settings is the Inspector route at /settings: connection to the Neotoma API, attribution policy on agent writes, retention, and appearance. The product Feedback flow is a separate top-level route at /feedback in the app (documented on its own page). Defaults match what an operator gets after running neotoma api start for the first time; many values are editable from the UI and persisted to local Neotoma config.

Sections

• Connection , API base URL, environment, SQLite database path, and the /health + /session probe that runs on save.
• Attribution policy , global mode (allow/warn/reject), minimum trust tier, and per-path overrides; the operator face of the AAuth contract.
• Retention , defaults are keep-everything; tier rarely-touched sources to cold storage or expire them after a window without dropping derived snapshots.
• Theme & accessibility , how Inspector handles appearance today (no separate theme panel in the Inspector app; docs site theme is separate).

Where these values live

Most settings are persisted to the local Neotoma config (the same one the CLI reads), so changes made in Inspector flow through to neotoma api start, MCP, and CLI on the next request. Attribution policy, in particular, can also be set via environment variables (NEOTOMA_ATTRIBUTION_POLICY, NEOTOMA_MIN_ATTRIBUTION_TIER, NEOTOMA_ATTRIBUTION_POLICY_JSON), the Inspector reads the resolved value and surfaces which source won.