<!-- Full-page Markdown export (rendered HTML → GFM). Source: https://neotoma.io/pt/inspector/settings Generated: 2026-04-27T12:48:41.866Z --> # 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](/inspector/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. inspector.neotoma.io/settings Inspector Neotoma Dashboard Conversations Turns Compliance Activity Feedback Entities Observations Sources Relationships Graph Explorer Schemas Timeline Interpretations Agents Agent grants Settings Settings Per-instance configuration connectedv0.12.0 Connection API base URLhttp://127.0.0.1:3080 Environmentprod DBneotoma.sqlite Attribution policy Allow anonymous writeson Require AAuthoff Hardware-only grantsadmin Retention Observationskeep all Source fileskeep all Timeline eventskeep all Theme & accessibility Colour schemesystem Densitycomfortable Motionreduce Settings docs grouping, four topics below map to dedicated pages; live /settings in the app is connection- and attribution-centric. ## Sections - [Connection](/inspector/settings/connection) , API base URL, environment, SQLite database path, and the `/health` + `/session` probe that runs on save. - [Attribution policy](/inspector/settings/attribution-policy) , global mode (`allow`/`warn`/`reject`), minimum trust tier, and per-path overrides; the operator face of the [AAuth](/aauth) contract. - [Retention](/inspector/settings/retention) , defaults are keep-everything; tier rarely-touched sources to cold storage or expire them after a window without dropping derived snapshots. - [Theme & accessibility](/inspector/settings/theme) , 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.