diff --git a/docs/config/index.html b/docs/config/index.html index 799b382..9cd0d6c 100644 --- a/docs/config/index.html +++ b/docs/config/index.html @@ -623,11 +623,28 @@

webhook

Point a GitHub webhook at https://your-server/webhooks/github with the push event. Set GITHUB_WEBHOOK_SECRET to match the webhook secret.

-

Authentication

+

analytics

+ +

Optional. Enables query logging and the built-in analytics dashboard at /analytics.

+ +
analytics: + enabled: false # Enable analytics (default: false) + log_queries: true # Log all search queries (default: true) + token: ${ANALYTICS_TOKEN} # Bearer token for /api/analytics endpoints + retention_days: 90 # Days to retain data (default: 90)
-

Pathfinder runs an anonymous OAuth 2.1 ceremonial flow for MCP clients. No user accounts, no sign-up, no dashboard — clients that perform the handshake receive a token whose subject is always anonymous. This satisfies MCP clients that require OAuth (claude.ai, newer Claude Code builds) while keeping Pathfinder a pure knowledge server.

+ + +

The analytics dashboard provides top queries, empty result tracking, and latency metrics. API endpoints: /api/analytics/summary, /api/analytics/queries, /api/analytics/empty-queries.

+ +

Authentication

-

There is nothing to configure in pathfinder.yaml. The only environment variable required is MCP_JWT_SECRET in production — see the Deployment Guide.

+

Pathfinder runs an anonymous OAuth 2.1 flow for MCP clients automatically — no config needed beyond the MCP_JWT_SECRET environment variable documented in the Deployment Guide. No user accounts, no sign-up, no dashboard — clients that perform the handshake receive a token whose subject is always anonymous. This satisfies MCP clients that require OAuth (claude.ai, newer Claude Code builds) while keeping Pathfinder a pure knowledge server.

OAuth endpoints

@@ -654,25 +671,6 @@

Bearer auth on /mcp and /sse

Clients that see the 401 challenge automatically discover the OAuth server, register, and retry with a valid token. Rotating MCP_JWT_SECRET invalidates all issued tokens at once — clients re-authenticate transparently on the next request.

-

analytics

- -

Optional. Enables query logging and the built-in analytics dashboard at /analytics.

- -
analytics: - enabled: false # Enable analytics (default: false) - log_queries: true # Log all search queries (default: true) - token: ${ANALYTICS_TOKEN} # Bearer token for /api/analytics endpoints - retention_days: 90 # Days to retain data (default: 90)
- - - -

The analytics dashboard provides top queries, empty result tracking, and latency metrics. API endpoints: /api/analytics/summary, /api/analytics/queries, /api/analytics/empty-queries.

-

Example Configs

Bash-only (no database)