Curate memory and reset sessions

Memory is deliberately small and explicit. Sessions are provider continuity that Helmhive binds to a profile, runner, and scope, and can reset.

Who can do this

Workspace Owners and Administrators, under AI → Memory and AI → Sessions.

Memory

1. Choose Add memory.
2. Enter a Title and the Memory text. Never store secrets or raw transcripts.
3. Under Memory details, pick a Scope (Workspace or one Service), a Sensitivity (Normal or Restricted), a Source such as a document, run, incident, or manual decision, and optionally an Expires at time.
4. Choose Save memory.

When a job whose profile allows memory is claimed, Helmhive injects at most the twenty most recently updated active records for its scope, bounded to two thousand characters each, labelled as context rather than authority. Archive stops future retrieval without changing work that already used a record. Governed change jobs receive no memory at all.

Sessions

A profile set to Resume or Fork creates a session binding after its first successful run, scoped to one profile, runner, provider, and workspace or service. The Sessions page lists bindings with the profile, provider, scope, runner, and last update. Provider session identifiers never reach the browser.

Reset session discards the stored continuity so the next job for that binding starts fresh. Governed change jobs never resume or fork.