Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.inlace.co/llms.txt

Use this file to discover all available pages before exploring further.

Each conversation in Lace is a session. A session bundles your chat messages, screen context, attachments, and any artifacts generated during the conversation into a single thread.

​
Why sessions are scoped

Sessions are tied to a specific chat thread. This means:
  • Screen context stays local. What Lace captures during one session doesn’t leak into another. If you’re switching between different tasks, each conversation only sees its own screen history.
  • Drafts are preserved. If you start typing a message, switch to a different chat, and come back — your draft is still there. Same for any selected insight tools or pending attachments.
  • Artifacts belong to their session. Summaries, analyses, and previews generated in a conversation stay with that conversation.

​
Starting a session

When you open a new chat, a session begins. Lace starts capturing screen context for that thread. If screen context is enabled, it tracks the window you’re working in — either the frontmost window automatically, or a specific window you’ve pinned.

​
The pill

When you minimize Lace, the session stays active in the background. The floating pill keeps you connected:
  • Click the pill to restore your session and the full overlay
  • Nudges appear on the pill when Lace spots something relevant to your workflow
  • The pill stays visible across all workspaces, so you’re never more than a click away

​
Session privacy

Each session is sandboxed to its organization. Your conversation data, screen captures, and attachments are scoped to the org you’re signed into. Switching organizations starts a fresh context.