Project memory
Decisions, files, and preferences for the current Space. Survives sessions, survives restarts.
Operator → Context
Memory that belongs to the workflow.
Generic chatbots forget every Monday. Spaces don't. Each one keeps the decisions, files, preferences, and state that matter for the work it's for — and Operator reads and updates that memory turn after turn.
Screenshot needed
Context inspector inside Operator: tabs for Project memory, Session state, Identity, Live state, Grasps, External data. Each tab shows a concise list of what's currently loaded — files, decisions, the open record, the connected MCP servers.
/shots/operator-context.pngLayers
Six things Operator knows.
Session state
What happened in this run — recent tool calls, intermediate results, the thread of the conversation.
Identity context
Who you are, what org you belong to, which Spaces you can access. Set once at the OS level.
Live state
The actual contents of the Space right now — the open file, the selected card, the row in front of you.
Grasps & tools
What the Operator already knows how to do, plus what this Space can call. Loaded with the Space, declared up front, never stitched in by prompt.
Outside data
MCP servers, web fetches, attached documents. Brought in deliberately, not assumed.