FlowLens
Chrome extension and MCP server that captures the full browser context of a bug and hands it to your AI coding agent as one link.
FlowLens is worth it if you already debug inside an MCP-compatible agent. The capture set — synchronized video, console, network, interactions, storage, navigation, system info — is genuinely more than a screen recorder gives you, and the MCP server means your agent consumes it without you rewriting a prompt. If you live in Claude Code, Cursor, or Copilot and spend real time re-explaining browser bugs, the Free tier is enough to judge it: unlimited local flows, 30 shareable flows a month. Teams at $11 per user per month adds Jira/GitHub/Slack and unlimited shares. It is a poor fit if you don't use MCP agents at all, or if you need capture outside Chrome.
Verified 5d ago · liveness 77/100 · cite: rightaichoice.com/tools/flowlens
- Solo developers debugging with MCP-compatible agents like Claude Code or Cursor
- Small teams that share bug reproductions by link
- QA engineers writing context-rich, reproducible bug reports for AI agents
- Freelancers who want to cut debugging back-and-forth with clients or agents
- Teams that don't use MCP-compatible AI coding agents
- Anyone who needs to capture bugs outside Chrome — desktop, mobile, Safari, or Firefox
- Users who need real-time collaboration on a live recording session
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip FlowLens if you don't debug with an MCP-compatible agent like Claude Code, Cursor, or Copilot, or if the bugs you chase happen outside Chrome — the extension captures browser context only, and nothing consumes the structured flow without the MCP server.
Hitting the Free plan's 30 shareable flows in a month blocks new shares until the next cycle or an upgrade — existing links stay accessible.
Free is genuinely usable for one developer: unlimited local flows, 30 shareable flows a month, instant replay, and MCP debugging. Early Access Teams at $11 per user per month is cheap for a per-seat developer tool and buys unlimited shares plus Jira/GitHub/Slack — well under most observability or session-replay suites. Enterprise, priced by contacting the founders, is the only place SSO/SAML, BYOC, and custom retention appear. Open source and non-profits get Teams free on request.
In short
FlowLens — Chrome extension and MCP server that captures the full browser context of a bug and hands it to your AI coding agent as one link. Best for Solo developers debugging with MCP-compatible agents like Claude Code or Cursor, Small teams that share bug reproductions by link, QA engineers writing context-rich, reproducible bug reports for AI agents. Free to start; paid plans from $11/user/mo.
What people actually say about FlowLens — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
10 mentions across 2 sources (Hacker News, Product Hunt) · researched Jul 3, 2026.
Average across the 2 sources that answered — each source counts once, not each post.
- +One-click capture of full browser context for AI agents.
- +Retroactively captures the last minute without pre-recording.
- +PII redaction done locally before any data upload.
- +SOC 2 Type 1 compliance adds enterprise trust.
- +Integrates with Claude Code, Cursor, Copilot, and Windsurf.
- −Very early-stage; limited independent user reviews available.
- −No clear self-hosting option for the cloud workspace.
- −Requires MCP-compatible agents – not universal.
- −One comment hinted flow needs fewer steps.
- −Pricing details beyond 'freemium' not transparent.
- • Exact Pro pricing not disclosed in community data
- • Cloud workspace may incur additional costs for storage or team seats
Viability Score
How well maintained and how widely used is FlowLens? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- One-click bug capture from Chrome
- Screen recording synchronized with technical events
- Network activity capture with full request/response data and filters
- Console output capture (errors, warnings, debug logs, stack traces)
- User interaction tracking (clicks, inputs, selectors, timestamps)
- Storage state capture (localStorage, sessionStorage, cookies)
- Navigation event capture (SPA-friendly, History API, hash changes)
- System info collection (browser, OS, screen resolution, timezone)
- Local PII redaction before data leaves your machine
- Encrypted recordings with user-controlled sharing
- Instant replay: retroactively capture the last minute of activity
- Shareable flow links readable by both humans and AI agents
- MCP server integration for AI agent debugging
- Projects and team member invites with shared flow links
- Local flows stored offline, unlimited on all plans
About FlowLens
FlowLens is a Chrome extension paired with an MCP server that records what actually happened when a bug occurred — synchronized screen video, console output, network request/response data, user interactions, storage state, navigation events, and system info — and packages all of it into a single shareable link that both a developer and an MCP-compatible coding agent can read. You click record, reproduce the issue, and share. Your agent then works from structured context instead of you pasting screenshots and log dumps into a chat window. FlowLens supports Claude Code, Cursor, GitHub Copilot, Windsurf, VS Code, Codex, and Gemini CLI. PII redaction runs locally before anything leaves your machine, recordings are encrypted, and local flows stay on your device with no cap on any plan. Instant replay buffers recent activity so you can save the last minute of a bug you didn't think to record. The Free tier gives unlimited local flows, 30 shareable flows per month, 3 projects, 3 users, and 5-minute recordings; Early Access Teams is $11 per user per month with unlimited shareable flows, Jira/GitHub/Slack integrations, 10 projects, 30 users, and 10-minute recordings; Enterprise adds SSO/SAML, BYOC, custom retention, and a dedicated SLA. Open source projects and non-profits qualify for free Teams access. FlowLens launched publicly in January 2026 and is built by Magentic AI, which describes itself as building developer tools for AI-native development.
Behind the Verdict
FlowLens solves a narrow, real problem well: the handoff between "something broke in the browser" and "my AI agent has enough context to fix it." The typical workflow it replaces is grim — screenshot the console, copy the stack trace, paste the network response, describe the clicks, and hope the agent infers the rest. FlowLens captures all seven signal types in one recording and exposes them through an MCP server, so the agent reads structured flow data rather than your paraphrase. The Instant Replay feature is the standout detail: a background buffer means you can recover the last minute of activity after a bug you didn't anticipate, which addresses the most common failure mode of any recording tool — you only wish you'd hit record. Privacy handling is designed for the awkward cases. PII redaction runs locally before data leaves the machine, recordings are encrypted, and sharing is user-controlled. Local flows never touch the cloud and are unlimited on every plan, including Free, which means you can debug a sensitive application indefinitely without paying or exposing data. SOC 2 Type 1 compliance is reported by the vendor. Open source projects and non-profits can request free Teams access by emailing flowlens@magentic.ai. The limits are structural, not incidental. Capture requires Chrome, so desktop apps, mobile, Safari, and Firefox are out of scope. AI-assisted debugging requires the separately installed MCP server, so the extension alone gives you capture and sharing but not agent integration. The Free tier caps shareable flows at 30 per month and recordings at 5 minutes; Teams raises that to 10 minutes, which is still short for long repro sessions. Teams is in Early Access via a waitlist, and Enterprise pricing is contact-the-founders. If your team doesn't work with MCP-compatible agents, the core value proposition doesn't apply to you — you'd be paying for a rich bug recorder with no consumer for the structured output. Compare against a general screen recorder if all you need is video, and against plain log dumps if your agent is already good at parsing raw text. FlowLens earns its place when the context transfer itself is the bottleneck.
Researching FlowLens? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas FlowLens actually fits — and what changes day-one when you adopt it.
A checkout form fails intermittently in staging. You install the FlowLens extension and MCP server, click record, reproduce the failure once, and share the resulting link into your Claude Code session.
Outcome: The agent reads the console error, the failing network request and response, and the exact click sequence without you copying anything, and proposes a fix in the same session.
A bug appears during exploratory testing that you didn't plan to record. Instant replay saves the buffered last minute of activity, and you attach the flow link to the Jira ticket from the Teams integration.
Outcome: The developer picking up the ticket gets video, console, network, and interaction data in one place instead of a written reproduction that needs a follow-up call.
The application handles regulated data and can't be recorded to a cloud service. You use local flows, which stay on your machine, with local PII redaction applied before anything would leave the browser.
Outcome: You get the full capture set offline and unlimited on the Free plan, with no usage ceiling and no data leaving your device.
Use Cases
- Record a bug reproduction and share one link with Claude Code so the agent works from real context instead of a rewritten prompt.
- Recover an unexpected bug you didn't plan to record using instant replay's background buffer of the last minute.
- Hand a teammate one link containing video, console, network, and interaction data instead of a written bug report.
- Attach full bug context automatically to Jira and GitHub tickets from the Teams plan integrations.
- Debug a sensitive application entirely offline using unlimited local flows that never upload to the cloud.
Models Under the Hood
as of 2026-10-18
Limitations
- FlowLens is a Chrome extension plus a separately installed MCP server.
- The extension alone handles capture and sharing; agent-driven debugging requires the MCP server, so there is a second install step beyond the browser.
- Capture only works in Chrome, which rules out desktop apps, mobile browsers, Safari, and Firefox.
- The Free plan caps shareable flows at 30 per month and recordings at 5 minutes; Teams raises recordings to 10 minutes and removes the share cap.
- Teams is currently in Early Access through a waitlist, and Enterprise is priced by contacting the founders.
- Local flows are unlimited on all plans, so offline and sensitive-data debugging is not usage-limited.
- Recordings use local PII redaction and encryption as described by the vendor, which reports SOC 2 Type 1 compliance.
as of 2026-10-04
Verification history
We have re-verified FlowLens 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
Showing the 6 most recent of 10 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published FlowLens tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0 forever
Ideal for
One developer debugging in Chrome with an MCP-compatible agent, working on up to 3 projects with up to 3 collaborators.
What this tier adds
Starting tier: unlimited local flows, 30 shareable flows per month, instant replay, MCP debugging, and 5-minute recordings.
Early Access Teams
$11 per user/month
Ideal for
Growing teams that ship fast and want bug context flowing into Jira, GitHub, and Slack for up to 30 users.
What this tier adds
Adds unlimited shareable flows, Jira/GitHub/Slack integrations, 10 projects, 30 users, 10-minute recordings, and priority support for $11 per user per month.
Enterprise
Custom
Ideal for
Organizations with security, compliance, or infrastructure requirements that need SSO, BYOC, and custom retention.
What this tier adds
Adds unlimited users, custom integrations, BYOC, SSO/SAML, custom data retention, advanced security controls, and a dedicated SLA; priced by contacting the founders.
Where the pricing makes sense
The company stage and team size where FlowLens's pricing actually pencils out — and where peers do it cheaper.
Free is genuinely usable for one developer: unlimited local flows, 30 shareable flows a month, instant replay, and MCP debugging. Early Access Teams at $11 per user per month is cheap for a per-seat developer tool and buys unlimited shares plus Jira/GitHub/Slack — well under most observability or session-replay suites. Enterprise, priced by contacting the founders, is the only place SSO/SAML, BYOC, and custom retention appear. Open source and non-profits get Teams free on request.
Setup time & first value
How long it actually takes to get something useful out of FlowLens — broken out by persona, not the marketing-page minute.
Solo developer: about a minute for the Chrome extension, plus a second short install for the MCP server if you want agent debugging — the vendor describes it as 1-minute setup. Team lead evaluating: install the extension, record one flow, and share a link, which you can do on the Free plan in under five minutes. Enterprise: add procurement time for SSO/SAML, BYOC, and custom retention, all of
Switching to or from FlowLens
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From manual screenshots and log dumps: replace the copy-paste prompt with one recorded flow link your agent reads directly.
- →From generic screen recorders: keep the video but add console, network, interaction, storage, navigation, and system data in the same capture.
- →From ad-hoc Slack bug reports: create a project, invite the team, and share flow links in the channel instead of written reproductions.
- →From Jira attachments of loose logs: use the Teams Jira integration to attach the full flow context to the ticket.
- ↗To a general screen recorder: export isn't the point — you'd lose the agent-readable structured context, keeping only video.
- ↗To manual log collection: copy console and network data out by hand before cancelling, since the value is in the packaging.
- ↗To an observability or session-replay suite: expect broader production telemetry but a heavier setup than a browser extension plus MCP server.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “FlowLens”, and we withheld 6: 6 could not be judged, because “FlowLens” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about FlowLens.
Official links
Tools that pair well with FlowLens
Common stack mates teams adopt alongside FlowLens, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Flowlens vs Locus Robotics
Choose Locus Robotics if you operate a high-volume warehouse needing flexible, scalable automation to boost productivity 2-3x. Choose FlowLens if you're a developer or small team debugging web applications with AI coding agents—it provides rich browser context to fix bugs faster. They serve entirely different domains, so the decision depends on your physical vs. digital workflow needs.
Flowlens vs Truleo
Truleo and FlowLens serve completely different markets: law enforcement intelligence vs. developer debugging. Choose Truleo if you need to connect police data sources for case leads; choose FlowLens if you want to accelerate bug fixing with AI agents by providing full browser context. There is no overlap in best-fit use cases.
Flowlens vs Presto Voice
Presto Voice and FlowLens serve completely different markets: Presto automates drive-thru order-taking for QSR chains, while FlowLens helps developers debug faster by feeding browser context to AI coding agents. If you run a multi-location fast-food chain, Presto's proven upselling and high non-intervention rates justify the custom pricing. If you're a developer using Claude Code or Copilot, FlowLens's free tier is a no-brainer for reducing bug-fix cycles.
Alternatives to FlowLens
View all
Chrome DevTools MCP
Open-source MCP server that gives coding agents live Chrome DevTools for debugging, traces, and browser automation.
Popular in MCP Servers & Agent Tooling
Frequently Asked Questions
Used FlowLens? Help shape our editorial sentiment research.