Configuration map
Settings live in three layers. Pick the layer that owns the thing you want to change, then look up the field. Each catalog sits next to the concept it configures.
| Layer | What it configures | You write it in |
|---|---|---|
| Flow | Actions, scopes, resources, auth, inbound transports | defineFlow({ ... }) |
| Runtime | Registered flows, models, stores, workers, heartbeats | createFlowState({ ... }) — often exported from fsdev.config.ts |
| Environment | Provider keys, store profile, intent overrides | .env.local and the host's secret store |
The flow layer describes what the app does. The runtime layer describes how this process runs it. Environment variables are the knobs you change without editing code: keys, which store profile is live, which model an intent should try first.
Narrative pages teach the concepts. The catalogs are field lists: name, type, default, what it does. Use them when you already know which object you're editing.
I want to change…
| Goal | Page |
|---|---|
| Add an action, expose session state, or bind a webhook | Flow options |
| Tune a generator, handler, sequencer, or router | Block options |
| Register flows, pick stores, enable durability, start a worker | Runtime options |
| Set API keys, pick a store profile, override an intent | Environment |
| Point the browser at a flow | Client options |
| Tune a task board, agent, or skills binding | Orchestration configuration |
| Tune working / episodic / semantic memory | Memory configuration |
Point fsdev at the same runtime the server uses | App configuration |
Map intent/chat to a fallback chain | Models |
| Persist across restarts | Persistence |
Seeing all three at once
Quick Start builds the smallest app that uses every layer: a flow file, a createFlowState handle, and a .env.local. The same handle mounts as your HTTP API and as the fsdev CLI — one object, two entry points. See App configuration.
What this section does not list
Pattern factories (supervisor, planAndExecute, …) and tool factories (fetch, search, bash, …) each have their own option object. Those fields live on the pattern or tool page. taskBoard is catalogued under Orchestration. The ecosystem overview is the index.
Testing harness options (testBlock, testFlow) live in Testing.