# Subtext — Agentic Session Review Source: https://subtext.fullstory.com.pgm.c5nprx.cc/ Site index for agents: https://subtext.fullstory.com.pgm.c5nprx.cc/llms.txt > Agentic Session Review is session replay built for agents. Your users hit the bug; your coding agent gets the real session — every click, console error, and network call — so it finds the root cause. Bring your own agent. Capture everything. Free to start. Agentic Session Review ## Session replay, built for agents. ### The structured, queryable, token-efficient context of every user experience. [Get Started](https://app.fullstory.com.pgm.c5nprx.cc/subtext/signup)[Find the story](https://subtext.fullstory.com.pgm.c5nprx.cc/story) ```sh npx @subtextdev/subtext-wizard ``` Context for: Claude Code Cursor Codex Devin LangChain In production at The Problem ### Why are humans still _watching sessions?_ The evidence is already in the session: the clicks, the console errors, the network calls, the DOM at the moment it broke. But connecting the dots between separate logging and analytics tools takes a human with time to watch, and for most sessions, nobody ever does. **Forensics still waits on a human.** Someone has to open the replay, scrub to the moment, and piece together what happened before any fix starts. **The evidence is scattered.** Session, console, network, errors, analytics — across tools, so the full picture only exists once a human assembles it. **You can't ask a replay what went wrong.** Most tools give you a video to scrub, not structured data for agents to interrogate, so finding one answer still means sleuthing across systems. How It Works ### Capture everything, integrate everywhere, review effortlessly, fix autonomously. Subtext captures your production sessions, drops links to them into the tools your agents already read, and gives your agent everything it needs to open a session, understand what happened, and take action. Capture #### Capture every session. A lightweight snippet captures full production sessions — efficient enough to keep them all, not just a sample. Link #### Links where agents look. A setup prompt drops Subtext session links into the tools your agents already read — Sentry, PostHog, support tickets, traces, PRs. Review #### Review without a human. Your agent opens the session, inspects the moments that matter, understands what happened, and takes action. [Subtext shows up wherever your agent already looks SentryPostHogMixpanelDatadogGoogle AnalyticsLangChainIntercomClickHouseOpenTelemetryLinear See all integrations →](https://subtext.fullstory.com.pgm.c5nprx.cc/docs/integrations/overview) Use Cases ### Wherever your agent works, Subtext is there. The same session context, dropped into the tools your team already runs. Pick a workflow to see how it plays out. Error investigationA spiking Sentry alert becomes a real session with the user impact, repro steps, and a validated fix. Agent trace reviewJump from a LangSmith trace to the human session behind it and see what the user actually did. Support triageA triage agent reads the ticket, opens the linked session, and builds the repro steps. Conversion drop-offPoint your agent at users dropping from the funnel and let it review the sessions to see what got in the way. ![A spiking checkout error in Sentry with a subtext\_session\_url tag linking to the captured session](https://subtext.fullstory.com.pgm.c5nprx.cc/home/sentry-error-spike.webp) 1 2 The Sentry alert links to the exact session a real user hit. Customers 🩷 Subtext Teams building on the frontier use Subtext to turn real sessions into fixes. > “We run our Sentry alerts through Subtext, so instead of a vague exception, we get the actual user impact, repro steps, and a validated fix. The screenshots of the broken UI a real user experienced motivate the owning team to prioritize it.” James Friend, Engineer, Clay Bring Your Own Agent ### Your data. Your agents. Subtext isn't another coding agent, and we don't force you into a proprietary AI ecosystem. You keep the workflows, tools, and agents you already trust; Subtext just hands them the unsampled session context they've been missing. We're the experience observability infrastructure behind your closed-loop workflow, so you keep total control over your models, your data, and your AI compute costs. Claude Code Cursor Codex Devin LangChain \+ your harness - ●Works with the agent you already run — no new harness to adopt. - ●Subtext supplies the session; your agent supplies the fix. - ●A CLI or MCP server any agent can call. - ●Purpose-built to be token and context-efficient — your agent sees only what matters. [Sightmap](https://sightmap.org/) follows the same principle: an open source map of your app’s views, components, and API requests, checked into your repo as YAML. Your agent reads real component names instead of DOM noise, with or without Subtext. Cost & Value ### Cheaply capture everything. _Stop sampling._ Tools built on rrweb — PostHog, Amplitude, Datadog, Sentry — cost so much to capture that teams sample: they keep a fraction of sessions and hope the bug was in one of them. Subtext makes capture cheap, so you don't have to choose. Capture every user experience. Capture #### Cheap enough to keep them all. Always-on session capture with a generous free tier — start free with ~10,000 sessions/month. No sampling, no choosing which sessions matter before you know. Agent credits #### Pay for the value, not the volume. You only spend credits when your agent reviews a session. Capture is the cheap part; the investigation is the part worth paying for. Free to start. No seats, no feature gates. [See pricing →](https://subtext.fullstory.com.pgm.c5nprx.cc/pricing) ### Give your agent _eyes on production._ Free to start. No seats, no feature gates. Capture every session and let the agent you already use tell you what happened. [Get Started](https://app.fullstory.com.pgm.c5nprx.cc/subtext/signup) ```sh npx @subtextdev/subtext-wizard ``` [Learn more about the wizard](https://subtext.fullstory.com.pgm.c5nprx.cc/wizard) Works with Claude Code, Cursor, Codex, and your own harness.