From a recorded Claude Code build
Claude Code missed 12 issues in its own plan. Here’s how to review yours with MegaLens.
No code to write. Works inside the Claude Code or Cursor chat you already use.
Free account. Your first review is free, no card needed.
What the independent reviewers caught
Claude Code reads findings like these and decides what to fix. The small line on each card is the finding exactly as it was recorded.
- CriticalOperational
The spending limit could not actually stop spending.
As recorded: No actual USD cost parsing from response.usage — cost cap is unenforceable
Caught by: MegaLens only
- CriticalOperational
Losing its database would make it redo drafts for old emails, in bulk.
As recorded: Bootstrap is :unread query + no gmail.modify — DB loss causes mass re-drafting of old mail
Caught by: MegaLens only
- HighSecurity
An email's own subject line could slip instructions to the AI.
As recorded: Email headers (subject, from, date) injected raw into LLM prompt — no sanitization
Caught by: Both (pre-audit missed headers)
- HighOperational
A crash at the wrong moment would create duplicate drafts.
As recorded: Draft-create → mark-processed crash window — duplicate drafts, no atomic guard
Caught by: MegaLens only
From a recorded build. Its plan review cost $1.25 and its mid-build code review $1.23. Read the full case study.
From the recorded build

Findings 6 to 15 of the plan review, as they came back in the recorded Claude Code build.
Three steps
Create a free account
Sign up free. No card needed, and your first review is on us.
Connect it to your coding tool
One command, pasted into the terminal on the computer where you use Claude Code. This step needs that computer, not your phone.
npx megalens-mcp setup
It finds Claude Code, asks for your connection token, which you copy from your MegaLens settings, and does the setup for you. Then restart Claude Code and type run megalens_status in the chat. A reply means you are connected.
Cursor and Codex each have their own short setup guide: Cursor · Codex
Using ChatGPT or Claude.ai in the browser? You need no command. Add MegaLens there as a connector and sign in: see the steps.
Ask for a review in plain English
Type either of these into your chat. Your coding tool takes it from there.
“Review this plan with MegaLens before we build”
“Run a MegaLens security audit on what we just built”
Example of what comes back in your chat
> Review this plan with MegaLens before we build
megalens_debate · done
Independent reviewers returned findings, including:
[Critical] No actual USD cost parsing from response.usage — cost cap is unenforceable
[High] Email headers (subject, from, date) injected raw into LLM prompt — no sanitization
I checked these against the plan. Both hold up. Updating the plan before we build.
Shown as text, not a screenshot. The two findings are real, from the recorded build.
What happens next
- The findings come back into your chat.
- Claude Code reads them and decides what to fix.
- You stay in the same conversation.
You do not need to leave your IDE.
Findings like these, on your own project, in the chat you already use.
Try it free on your projectFirst review free. Then $5 credit for $0.50, or pick a plan.
Questions
Do I need to know how to code?
What is an MCP?
How can I try it?
Will it send my code somewhere?
Does it replace Claude Code?
What does it cost after the free review?
Two ways to pay.
A plan: Plus and Pro include a monthly allowance of reviews, with model usage included, from $19 a month. MegaLens selects up to four reviewing models.
Pay as you go: you keep a balance with MegaLens and each review is charged from it, never more than $3 for one review. In a recorded Claude Code build, the plan review cost $1.25 and the mid-build code review $1.23. Your free review comes first, and $5 in credit covers about four reviews that size.
Full details on the pricing page.
To see it for yourself, the case study has every finding from the recorded build and what Claude rejected. Read the recorded build