Usage & Features

Advanced settings

Experimental Engine, local audit logging, and hub-settings.json reference for automation preferences.

On this page

The hub stores most preferences in CHAIN_HOME/.chain-hub/hub-settings.json. Many toggles in Settings save immediately when you flip them — no separate Apply button.

Open Settings → Advanced → Advanced preferences for automation and diagnostics controls.

Experimental Engine

Default: off

When enabled, Chain Hub can run pipeline automation without manual confirmation on every step:

Brain → Pipeline → Clean up & continue and Process inbox (API: POST /api/pipeline/cleanup-and-continue, POST /api/pipeline/process-inbox)
Settings → Brain → Automatic inbox cleanup — only takes effect when Experimental Engine is also on

Experimental Engine does not auto-apply skill edits. Proposals still require explicit approval in For you before Apply.

If automation is disabled, the hub returns a clear error asking you to enable Experimental Engine in Settings → Advanced.

Diagnostics

Default: on

When enabled, Chain Hub keeps a local audit log so you can review pipeline and memory activity later. This is for your history only — nothing is sent to Chain Hub servers or third parties.

Pipeline automation runs → learnings/pipeline-runs.jsonl
Project memory and pipeline apply events → memory/workspaces/<id>/audit.jsonl

View the log in the hub under Brain → Pipeline → Activity, or open the JSONL files directly under CHAIN_HOME.

Turning diagnostics off stops new writes only; existing history stays readable.

hub-settings.json reference

Advanced preferences map to the advanced block:

{
  "advanced": {
    "experimentalEngine": false,
    "diagnostics": true
  }
}

Other common blocks in the same file:

Block	Hub UI	Purpose
`brainPipeline.autoTriage`	Settings → Brain	Auto cleanup when opening Pipeline (requires `experimentalEngine`)
`skillLibrary.trackingEnabled`	Skills → Library Health	Local skill invocation tracking in `brain.db`
`assetUpdateChecks`	Settings → Advanced → Content update checks	Periodic upstream drift checks

See Library Health and Continual learning for related features.

API

Method	Path	Purpose
`GET`	`/api/config/hub-settings`	Read all hub settings
`POST`	`/api/config/hub-settings`	Merge partial settings (same shape as `hub-settings.json`)

Example — enable Experimental Engine from a script:

curl -s -X POST http://127.0.0.1:4321/api/config/hub-settings \

-H 'Content-Type: application/json' \

-d '{"settings":{"advanced":{"experimentalEngine":true}}}'

(Replace host/port with your running chain hub or dev proxy.)