Claude Subtext connectorWhat Claude can do in your Subtext account.
The Claude Subtext connector exposes 15 tools. 9 read your recorded sessions and rules, 6 change something, and none is left undescribed. Below: how Claude investigates a session, what it masks, and what takes effect with no way back.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your debugging
Subtext, a Fullstory brand, records real user sessions on your web app. With this connector, you hand Claude a session link and it investigates the session itself: pages, screenshots, console, network. The publisher describes it as session replay built for agents, aimed at finding the root cause of a problem in a real production session.
Get the gist of a session fast. review-summary returns a summary of what happened without even opening the session; when that isn't enough, review-open opens it with its event map and a short account of how it unfolded.
Go to the exact moment. review-zoom narrows the investigation to a time window at the level of detail you need, and review-snapshot captures the screen at that instant along with the component tree.
Keep personal data out. privacy-propose spots elements in a session that look like personal information and suggests masking rules, which privacy-create then saves in preview mode before any wider rollout.
Worth knowing: nothing shows up until Subtext's capture snippet is installed in your app. Several reads cost a credit. URL and network rules apply to every session immediately, with no preview and no deletion from Claude. And nothing runs by itself: Claude reviews no session on a schedule. That's an automation tool's job, a different trade; the Integrations hub covers that side.
The vocabulary in one minute
Five words you'll meet while connecting Subtext.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can take it back later.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service in the first place.
Connect Subtext to Claude in three steps
- 01
Find Subtext in Claude
In Claude's settings, open Customize, then Connectors, and locate Subtext in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first so that each member can connect afterwards.
- 02
Start the connection
Click Connect on its row, then sign in to Subtext in the window the service opens itself. If the link breaks at some point, use Disconnect and connect it again from that same row.
- 03
Read the authorization screen
Before accepting, read the authorization screen: it belongs to the service, not Claude, and it decides what the access covers. Anything granted there can also be withdrawn later from your account on the service.
The 15 tools, grouped by what they do
Subtext gives Claude 15 tools: 9 that read your account, 6 that change something in it.
Two groups: what Claude reads, and what it changes in your rules and reviews. Names stay exactly as Claude shows them.
- 9 read
- 6 write
What Claude reads (9)
9 toolsNine tools that look at your sessions and privacy rules without touching them.
privacy-list
Shows the element-block rules in both preview and live scope, so you can audit what is already masked and spot redundant rules or promotion candidates.
privacy-propose
Walks every page of a session, spots elements that appear to hold personal information and suggests selectors with a rule name and the data type. Nothing gets saved.
review-snapshot
Grabs the screen of an open session at a given moment: an image, the component tree with component IDs, and each element's bounding box.
review-list-sessions
Returns your organisation's most recent sessions, newest first, or one user's sessions based on their email address or user ID.
review-open
Opens a session for review and returns its event map plus a short account of how it went, along with the identifiers used by follow-up calls.
review-summary
Produces a static summary of what happened in a session without opening it. It's the cheapest call for a first read.
review-zoom
Narrows the review of an open session to a time window with adjustable resolution, like a magnifying glass moved along the recording. Subtext calls it the live lens, and it works on a session already opened with review-open.
privacy-url-list
Lists every privacy rule applied to page addresses, with each rule's condition and the parts it redacts, without altering any of them or their scope.
privacy-network-list
Shows every rule applied to recorded network calls: the URL pattern it targets and how request and response bodies are handled.
What Claude changes (6)
6 toolsSix tools that touch your masking rules or your reviews. No source details their confirmation, so the general rule below applies.
privacy-create
Approval: see the ruleSaves element-block rules from selectors, scoped to preview sessions only: matching elements are masked when a session opens in preview mode, so you can test before a broad rollout.
privacy-delete
Approval: see the ruleRemoves preview rules for good. Only preview rules can go; live ones are protected.
privacy-promote
Approval: see the ruleMoves preview rules into live scope: every new session captured then masks the matching elements. The rule becomes protected and can no longer be deleted through the agent tooling.
review-close
Approval: see the ruleCloses the session under review and records structured feedback: which sessions were reviewed, for what purpose, and whether it helped. It also frees server resources.
privacy-url-create
Approval: see the ruleCreates a privacy rule for page addresses, or updates one in place by its ID: a condition for the addresses it applies to, exclusions for the parts to redact.
privacy-network-create
Approval: see the ruleCreates a rule for network calls matching a URL pattern, or overwrites the existing one, and sets how request or response bodies are handled.
What Claude asks you before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the conversation, right when it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time. They can also cap what a connector may do across the organisation, keeping session review open and closing masking rules, for example. Nobody bypasses that from their own account, and Claude sees nothing beyond your own access to Subtext: a session your account can't open stays closed to it too.
Which plans it's available on
Of the 819 sheets in the official directory, none shows availability by plan. For Subtext as for the rest, the connector-by-connector answer isn't published anywhere.
The general rule, though, is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before each member can connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector isn't an automation: Claude calls these tools while it answers you, and nothing kicks off when a session crashes. Only the publisher, Fullstory, documents this connector.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The directory's partner badge isn't a security audit, and Anthropic says so on every sheet: it doesn't choose a publisher's tools or vouch for how they behave. Connect only what comes from a publisher you trust, here Fullstory, and read its documentation first. Other connectors are listed on the Claude integrations page.
Need help connecting Subtext to Claude?
A person reads every message.