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.

Lace runs quietly in the background. It captures your screen, parses UI elements, and builds an interaction graph over time. When it finds something worth acting on, it surfaces a nudge — an insight card grounded in evidence, never hallucinated.

​
Floating pill

The pill is a small capsule that floats on your screen. It shows what Lace is doing: idle when no session is active, watching when capture starts, a breathing animation while parsing, and ready when screen context is available. Hover to reveal controls, or press ⌘O to open the overlay. Press ⌘L to restore it if minimized.
Lace floating pill showing a nudge headline

​
Nudge bar

When Lace detects an adoption signal worth surfacing, the pill expands into the nudge bar — a wider surface below the capsule showing a nudge headline and an Accept button.

​
How nudges are generated

1

Provide context

Upload transcripts, PRDs, or customer feedback.
2

Lace extracts signals

Signals are extracted from documents (data-grounded) or detected by heuristic rules on your interaction graph (pattern-grounded). If Lace can’t back a claim with evidence, it doesn’t surface it.
3

The nudge bar appears

The pill expands into the nudge bar showing the headline and an Accept button.

​
Insight cards

Tap Accept on the nudge bar to open the full insight card. Each card includes a headline, supporting evidence traced back to its source document, and an adoption consequence tag.
Lace insight card showing a retention risk signal with source evidence and approve/dismiss buttons
Cards show up to three at a time in a carousel. Each one points to a specific part of the UI.

​
From nudge to decision

Approve a nudge and it becomes a persistent decision anchored to the UI area it references. Your coding agent can query it through MCP and ship the fix.
  1. Detect. The interaction graph identifies a signal with evidence
  2. Surface. The nudge bar appears with the headline
  3. Review. Accept to see the full insight card
  4. Decide. Approve to create a decision, or dismiss
  5. Execute. Your coding agent queries the decision through MCP and ships the fix