Sessions

How Lace scopes ephemeral screen-context sessions to chat threads and layers user, project, and thread memory for persistent context.

A chat is the durable conversation thread. A screen-context session is the live capture lifecycle attached to that chat. One chat can have many sessions over time as you start, stop, or switch capture. This allows users to control when they want Lace to view their screen.

Scoping

• Screen context is thread-scoped. Live captures and cached screen context are attached to the active chat.
• Drafts are preserved. Draft input is keyed by chat.
• Artifacts belong to their thread.

Capture lifecycle

• Draft chats can auto-start capture.
• Existing chats start capture via the recorder control.
• Navigating away stops the live session.
• Starting capture for a different thread stops the previous one.

Memory

Lace keeps memory separate from screen-context sessions.

• User memory stores durable preferences for the current user and organization, such as communication style or recurring constraints.
• Project memory stores durable project context, including current goals, ongoing tasks, and constraints to respect.
• Thread memory stores recent conversation messages for the current chat. Older messages may be compacted into summaries so Lace can still reference earlier context.

Screen-context captures remain scoped to the active chat session. Memory is only added when a turn produces durable facts worth preserving, and project memory is only attached when the chat belongs to a project.

The interaction graph carries cross-session context within a project.

Privacy

Sessions and memory are scoped to your organization. User memory follows the current user within that organization, while project memory stays attached to its project. Switching organizations starts a fresh context.