Settings Persistence

These endpoints allow clients to persist account-level dashboard preferences on the server. Preferences are saved as a JSONB object on the user's row and are not part of the zero-knowledge encrypted memory layer.

1. Retrieve Settings

Fetch user dashboard settings. If no settings have been saved yet, default fallback settings are returned.

Request URL

GET /settings

Response (200 OK)

{
  "settings": {
    "project_name": "default-project",
    "project_desc": "Main trading agent workspace",
    "session_lock": false,
    "hosted_sync": true,
    "telemetry_opt_in": false
  }
}

2. Update Settings

Partially update one or more settings fields. Unknown parameters are ignored, and malformed types will throw a 400 validation error.

Request URL

PUT /settings

Request Body Schema

{
  "project_name": "production-agent-v3",
  "telemetry_opt_in": true
}

Response (200 OK)

Returns the fully updated settings configuration:

{
  "settings": {
    "project_name": "production-agent-v3",
    "project_desc": "Main trading agent workspace",
    "session_lock": false,
    "hosted_sync": true,
    "telemetry_opt_in": true
  }
}