Sightmap is our open-source labor of love. Don't miss out on giving your agent a proper runtime map! Such a simple way to improve agent efficiency on verification task and browser use.
🚀
Had to test out the Fable 5.1 hype for myself.
Verdict? LFG.
Check out this one-shot landing page concept that brings our new open-source project to life: sightmap.org/building/
For agents building customer facing user experiences and interfaces, you can now ground their context with real user journeys @subtextdev
Replying to @bot
@bot is ✨ customer support/success.
Bots can be triggered from a new Slack message or emoji, directly review recent user sessions with @subtextdev, find the root cause, and kick off a @cursor_ai agent run with the fix.
What used to take five handoffs is now on autopilot.
Next up: @bot for customer insights.
Set up a new analyst bot with @subtextdev to review sessions for you every day. Get a customer pulse briefing delivered to your inbox or team @SlackHQ channel.
Post a @subtextdev + @bot video and DM me the link for a free plan upgrade.
Replying to @benjitaylor @bot
Add the @subtextdev plugin to @bot and have it triage customer support bugs and product friction. Just add a routine on a support bot with a Slack emoji listener.
Great use case for customer support and success teams!
Replying to @subtextdev
@subtextdev is now available in @bot!
You can have an agent review customer sessions directly and find bugs, support issues, and ux friction.
Try Subtext for free today and experience ✨ of agentic session review.
We open-sourced an important component to how agents can curate the semantic layer for frontend/behavioral data: sightmap.org
Replying to @lukerramsden
This is 🔥
If you want Devin to watch sessions recordings that are directly connected to the issue, I think you'll like @subtextdev - it's a new session capture product and set of MCP tools our team just launched built for this exactly background agent SRE use case.
See how it works live: subtext.fullstory.com/playgr…
We created @subtextdev because every coding agent needs to ground their reasoning in real user experiences. Looking at the codebase and logs simply isn't enough.
If you're an engineer/builder/pm/designer, you already know that. You have spent hours watching user sessions (replays) to truly understand bugs, diagnose root cause, and discover how your users actually experience the features you ship.
If that's you, it's time to let your coding agent do the work.
We shipped a simple but powerful addition to the Subtext MCP tools this week: subtext.fullstory.com/docs/s…
Now your agent can easily find a specific user's most recent product session (say from a support ticket, @intercom chat, or @SlackHQ message) and automatically review the experience, triage the issue, and draft a fix/PR.
When you capture everything, your agent can be "always-on, 24/7". No need for legacy bug reporting like jam dev
Agents need to eyes on production so they can close the feedback loop on the user experiences they build and ship.
That’s why we built @subtextdev
Replying to @subtextdev
@subtextdev is officially in the @OpenAI Codex plugin marketplace!
For everyone building apps, it’s so convenient to have Codex (or Claude, Cursor, Linear, etc) review a user’s recent session and give you a detailed summary or root cause analysis for a bug report.
Go try it free today!
Subtext is live in the Linear directory.
Issues feed the Loop a session link and it runs the investigation. The agent gets tools to zoom into screenshots, network calls and console errors, root cause posted as a comment before an engineer or coding agent opens the issue.
linear.app/integrations/subt…
RT @chiplay: Subtext is live in the Linear directory.
Give a triage Loop a session link and it runs the investigation. Real production ses…
It’s true
Most important thing for self-driving cars is a solid vision and LIDAR system. Same is true for AI agents. This is exactly why we built @subtextdev, which you can plug into any agent (including Posthog's).
Subtext retweeted
What's the difference between good ol' human Session Replay (HSR) and Agentic Session Review (ASR)? HSR is pretty much Netflix. Hit play and watch. Rewind if you miss something.
ASR is different. Agents don't hit play. They ask a question, get a map of the whole visit, then zoom into just the part that answers it. No rewinding through 42 seconds to find the one moment that mattered.
In this post, @who_cayres and @jgw spell it out better than I ever could. Enjoy.
subtext.fullstory.com/blog/a…
I had a lot of fun working on the brand identity and mark for @subtextdev this week. It's the first time I've scratched that itch in a while and I'm pretty happy with where I landed.
I'd love to hear what you think.


















