Triage issues with evidence from real user sessions

Overview⁠

Subtext is session replay built for agents. When an issue includes a Subtext session link, agents in Linear can efficiently review the real production session—including screenshots, component trees, console and network activity—and post a diagnosis with evidence before a coding agent or engineer picks the issue up.

How it works⁠

Subtext captures production web sessions through a lightweight snippet, reconstructed on demand so an agent can inspect any moment without a human scrubbing the session replay. Session links flow into Linear issues from the places bugs already originate — error trackers, support tools, analytics events, or a pasted URL in the issue description.

When an agent picks up an issue during triage, it checks the description and comments for a Subtext session URL. If one is present, a triage Loop opens the session with Subtext’s MCP tools: it steps through the moments around the problem, zooms into the relevant network requests and console errors at the resolution it needs, and compares what the user actually saw against what the UI intended. It then posts a structured triage comment grounded in the session: root cause, steps to reproduce, and visual evidence attached.

From there, Linear routes the work. A delegated coding agent or a Loop inherits the issue with full context: the screenshot of the failure, the component state behind it, and a verified reproduction path. The same MCP tools work with whatever agent harness your team runs, so the diagnosis travels with the issue rather than living in a separate tool.

Configure⁠

To get started, your workspace must be on a Linear Business or Enterprise plan, since Loops are available on those plans and draw from your workspace’s AI credits. The team you’re configuring must have Triage enabled. Additionally, a workspace admin will need to allow the Subtext MCP server before it can be used. Then. you can follow the Install and configuration guide