Question 1

What does malveon actually do?

Accepted Answer

You give your AI a to-do list. The AI writes code and says it’s done. malveon reads that code and tells you, item by item, whether each thing is really built and hooked up, broken, missing, or half done, and shows you the exact line in the code that proves it. Each report opens with one verdict: Found problems, Worth a look, or Nothing found in the code I read. It also flags what your AI added that you never asked for, what it broke along the way, and what it left unfinished.

Question 2

What can’t it check?

Accepted Answer

It doesn’t click through your app, so it can’t tell you whether it works for a real person. The optional screen-layout check opens pages in your own Chrome or Edge, and can start your app for you with a command you give it and approve once. It lists overlapping text, cut-off content and low contrast, but only at the widths and themes it tried. Tracing what gets saved works for apps that store data with Supabase, Prisma, or Drizzle, and pages are traced for Next.js, Nuxt, SvelteKit, Remix, and Astro apps. Other database libraries and GraphQL aren’t read yet. Anything it can’t check, it says so instead of guessing.

Question 3

Do I need to be a programmer to use it?

Accepted Answer

You need to be able to paste one line into a terminal, or install an extension in VS Code or Cursor. After that it runs on its own. The answers are plain words, and each one points to the exact spot in the code, so you or a developer can check it.

Question 4

Is this just another AI checking my AI?

Accepted Answer

No. malveon doesn’t use an AI to judge anything. It reads the code itself, the same way every time, so the same code always gets the same answer.

Question 5

What does “hooked up” (CONNECTED) mean?

Accepted Answer

The feature is built and connected: the button on the page really reaches the code that does the work, and a Save really saves. It doesn’t mean every detail of your business rules is right, and it never means malveon clicked through your app.

Question 6

Does my code leave my computer?

Accepted Answer

No. Your code, file names, plans, and what you type to your AI stay on your computer. malveon sends a few anonymous usage signals: your operating system, computer type, malveon’s version, which command ran, the name of the AI tool or editor that ran it, and whether a check came back clean or blocked. Nothing about your project, and no location. They can’t be turned off in the terminal or when your AI agent runs malveon; the editor extension follows your editor’s telemetry setting. It also checks GitHub once a day for a newer version; turn that off with MALVEON_NO_UPDATE_CHECK=1.

Question 7

Does it work with Claude Code, Cursor, Codex, or Antigravity?

Accepted Answer

Yes. Your AI can run malveon itself and get the same report you would see. After a one-time setup, malveon can also read the prompts you type to those tools. When a decision is needed, like running commands on your computer, malveon asks you, never the AI.

Question 8

Does it notice things my AI broke?

Accepted Answer

Yes. malveon compares your code with how it was when you started the task. If a button that used to work now calls something that doesn’t exist, or a leftover debugging line or a secret key shows up, it says so and points to the line. It only knows a short list of common mistakes plus that before-and-after comparison, so it is not a general bug finder.

Question 9

Does it notice things my AI added that I didn’t ask for?

Accepted Answer

Yes, for six kinds of thing: new requests and server addresses, new pages, new database tables, buttons that change your data, and new packages. It lists the ones that neither your plan nor your own prompts asked for (your AI’s own summary doesn’t count as asking), and it also lists changed files that nothing you wrote points at, when your prompts name code. It can’t see a button that only changes how the page looks, or a button whose handler lives in another file. It lists these for you to review without blocking your work.

Question 10

What if my button does nothing?

Accepted Answer

If your plan says a button should send something and the button has no click handler, or one that does nothing, malveon marks that line half done and points at the button. It reads the code only, so a button that is wired up but still misbehaves when clicked is something only you can try.

Question 11

Does it check what my AI says about its own work?

Accepted Answer

Yes. When your AI writes “the refund route is now working” in a notes file, a commit message, or its final message, malveon looks that up in the code like a line from your plan. If the code says otherwise, that is shown as a problem. It reads English only, and it ignores sentences that hedge, plan, or name nothing it can look up.

Question 12

What about vague requests like “make it better”?

Accepted Answer

A request that names no page, button or file leaves nothing to look up, so malveon can’t say whether it was met. Instead it asks your AI to say what would show it is done, keeps those words, looks up whatever they name, and lists the rest for you to confirm. It makes a hollow “done” easy to spot; it doesn’t decide for you.

Question 13

What counts as a run?

Accepted Answer

A check you start yourself: typing malveon, or your AI or editor running a check when you ask. Checks that run on their own in the background, like the watcher, never count and are never stopped. Your first 150 runs are free.

Question 14

Will it block my commit or stop my AI?

Accepted Answer

No. malveon reports and exits normally. If you want your own build to fail on its findings, you can read its JSON output in your build script.

Question 15

Do I need a plan to start?

Accepted Answer

No. Type malveon in your project folder and it lists what is wrong right now, with no plan and no setup: a button that does nothing, a call to an address nothing serves, an import that cannot work. It never starts your app, it shows the first three problems, and a short list is not proof that everything works. You can try it without installing: npx malveon.

Question 16

Can it check work my AI already did?

Accepted Answer

Yes. Run malveon with --since and the point before the task, for example malveon --since HEAD~3. It looks at what changed since then and says what was added that nothing asked for, what broke, which tests were removed and what was left unfinished. With no plan, your commit messages stand in for what you asked for, which is a weak stand-in, and the report says so.

Question 17

What if my plan is messy?

Accepted Answer

A simple checklist is enough. Headings and notes are skipped, with the reason shown. If an item is too vague to check, it is marked as not checked, never as a failure, and it tells you what to add, like the page or button you mean.

Question 18

Which apps can it read?

Accepted Answer

The screens of apps written in JavaScript or TypeScript (including Next.js, Nuxt, SvelteKit, Remix, and Astro), and servers written in Python, Go, JavaScript, TypeScript, Rust, Java, Ruby, PHP, or C#, including NestJS, Django, and tRPC routes.

Question 19

Can I fail my own build on its findings?

Accepted Answer

Yes, in your own script. malveon never stops anything itself: it reports and exits normally. To make your build fail, read its JSON in your build script with malveon --json -.

Question 20

How much does it cost?

Accepted Answer

Your first 150 runs are free, for personal or commercial work, with no account and no credit card (the 150-Run Free Trial). A run is a check you start yourself; checks that run automatically in the background never count. After that, Malveon Pro is $19 a month plus tax for unlimited runs, and you can cancel any time with one command. For a team plan, write to ladson@malveon.com. See the pricing page. malveon is partly open source: the code that reads your project and decides each plan-line verdict is published under the Apache License 2.0 in the public GitHub repo. The program you download as a whole also contains closed code, and is used under the Malveon Beta License. A version you already have never starts charging you.

Refunds and cancelling

Cancel any time

Full refund within 14 days

After 14 days

Your rights under the law

Questions