Inspector, Settings · Connection (Markdown)

# Inspector, Settings · Connection

The Connection panel tells Inspector which Neotoma instance to read from. It's the first place to look when the UI is empty, returning zeros, or showing the wrong environment.

inspector.neotoma.io/settings#connection

Inspector

Neotoma

Dashboard

Conversations

Turns

Compliance

Activity

Feedback

Entities

Observations

Sources

Relationships

Graph Explorer

Schemas

Timeline

Interpretations

Agents

Agent grants

Settings

API connection

Base URL

http://127.0.0.1:3080

Environment

proddevsandbox

DB path

~/.neotoma/neotoma.sqlite

Server

healthyv0.12.0 · pid 48132

Last probe

/health

200 · 4ms

/session

tier · software

/stats

12.4k entities

Connection panel, API base URL, environment, DB path, and a one-click health probe.

## Fields

- **API base URL**, the HTTP endpoint serving Neotoma. Defaults to `http://127.0.0.1:3080` for prod and `http://127.0.0.1:3180` for dev. Override when running against a remote tunnel or a non-default port.
- **Environment**, `prod`, `dev`, or `sandbox`. Used as a label across the UI (timeline filters, agent badges) so you don't mistake one instance for another. The value matches the `--env` flag the CLI uses for server commands.
- **DB path**, the SQLite file backing this instance. Read-only here; surface it so operators can copy it into a backup or the [CLI's](/cli) `storage recover-db` flow.
- **Server**, version, pid, and uptime reported by `/health`. Mismatch here is the first sign you're hitting a stale process.

◆

## Health probe

Saving Connection changes triggers three probes against the new base URL:

1. `GET /health`, verifies the server is up and responding.
2. `GET /session`, fetches the resolved attribution tier and the policy decision (so the [Attribution policy](/inspector/settings/attribution-policy) panel can render an accurate "current state").
3. `GET /stats`, pulls entity counts so the dashboard and [Entities](/inspector/entities) page light up immediately.

If any probe fails the panel surfaces the exact HTTP status, body, and latency, and refuses to apply the change so you don't lose the working connection mid-debug.

◆

## Multiple instances

Inspector remembers recent base URLs and lets you switch between them without a reload. This pairs with the CLI's connect-only startup, agents and humans share the same set of running ports, and the Inspector tabs the active one.