State
PreviewWhat the runtime persists, where it lives and how it is scoped.
State is partitioned by lifetime. Understanding which store holds what explains resumption behaviour, memory retention and privacy guarantees.
Scoping rules#
- Run state is discarded after the retention window unless promoted to an artifact or long-term memory.
- Sandbox filesystems are ephemeral by default; promote files explicitly with
artifacts.publish. - Nothing in run state crosses a workspace boundary, including derived embeddings.
- Model context is assembled per step from state — it is never the canonical store.
class="tok-com">// Promote a sandbox file to a durable artifact
await pimsy.artifacts.publish({
runId: class="tok-str">"run_7c1a9d",
path: class="tok-str">"reports/latency-analysis.md",
retention: class="tok-str">"90d",
visibility: class="tok-str">"workspace"
});Last updated 2026-09-06

