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.
Use Lace with your coding agent
Connect Lace to Claude Code, Cursor, or Codex so your coding agent can read approved decisions and ship the fix — no copy-pasting required.Lace surfaces adoption signals as nudges. When you approve a nudge it becomes a decision — a scoped change request with evidence, screenshots, and a suggested fix. The MCP server lets your coding agent pull those decisions, see exactly what needs to change, and write the code.
Get started
Run the install command for your coding tool:- Claude Code
- Cursor
- Codex CLI
How it works
Lace surfaces a nudge
The interaction graph detects an adoption signal and shows it as an insight card.
Your agent queries Lace
It calls
list_decisions, picks one, then calls apply_decision to get screenshots, targeting, and step-by-step instructions.Technical reference
MCP server
The Lace MCP server is registered under the namelace and exposes three tools:
list_decisions
Returns all approved product decisions as a summary list.
Parameters: none
Returns:
| Field | Type | Description |
|---|---|---|
id | string | Unique decision identifier |
headline | string | Main decision headline |
insightHeadline | string | null | The specific insight that was approved |
elementEid | string | null | Element ID within the UI |
appName | string | null | Application where the decision applies |
approvedAt | string | ISO timestamp of approval |
get_decision
Returns full details for a single decision — the card, element targeting, bounding box, and inline screenshots. Use this for browsing and inspecting decisions.
Parameters:
| Parameter | Type | Description |
|---|---|---|
id | string | Decision ID from list_decisions |
| Field | Type | Description |
|---|---|---|
id | string | Decision identifier |
card | object | Decision card with headline, body, evidence, and insights |
insightIndex | number | Which insight was approved (index into card.insights) |
elementEid | string | null | Target element ID |
bbox | array | null | Normalized bounding box [left, top, right, bottom] in 0-1 coordinates |
screen | object | {appName, windowTitle, shotId} |
approvedAt | string | ISO timestamp |
apply_decision
Returns everything needed to implement a decision: screenshots, the decision card, element targeting, and step-by-step implementation instructions. Call this instead of get_decision when your agent is implementing a change.
Parameters:
| Parameter | Type | Description |
|---|---|---|
id | string | Decision ID from list_decisions |
- Annotated screenshot (JPEG, when available)
- Raw screenshot (JPEG)
- Implementation prompt with:
- Decision card (headline, approved insight, suggested fix, evidence)
- Target element (element ID, bounding box, screen info)
- Step-by-step instructions to locate the element and implement the fix
- Constraints on what not to modify
Config file locations
| Tool | Config file |
|---|---|
| Claude Code | ~/.claude/settings.json |
| Cursor | ~/.cursor/mcp.json |
| Codex CLI | ~/.codex/config.toml |
Troubleshooting
Agent can't connect to Lace
Agent can't connect to Lace
The Lace desktop app must be open and signed in. Open the app and retry.
No decisions returned
No decisions returned
You need to approve nudges first. Open Lace, review the insight cards, and approve at least one.
Agent doesn't recognize the MCP server after install
Agent doesn't recognize the MCP server after install
Restart your coding tool fully (quit and reopen), then confirm the Lace server appears in your MCP settings.
Screenshots are missing from decision details
Screenshots are missing from decision details
Screenshots are stored locally alongside the Lace app data. If they were deleted or the app was reinstalled, the decision will still return card and targeting data but without images.