# Keep state across runs :::note This tutorial is a stub. The mechanism it covers is documented today under [Pipelines / Config](/pipelines/config) (the `state` option). ::: An orchestrator pipeline can persist JSON state between runs (BIP-22). Setting `state: true` exposes `read_pipeline_state` / `write_pipeline_state` tools to the orchestrator; state lives in `/state/.json` on the daemon host. This is how a pipeline keeps an index, a cursor, or a set of already-handled items across firings. This lesson will build that with the `tdd-refactor` index/cursor/reviewed pattern as the worked example. Until it lands, see the `state` row in [Pipelines / Config](/pipelines/config). State applies to orchestrator pipelines on local backends only.