Malveon

Checks whether your AI coding agent really built what your plan and your prompts asked for, by reading the code, never by asking the agent.

What you see

• Status bar: malveon: clean or malveon: blocked (N). Click it to open the results.
• Problems panel: a red squiggle on the plan line that isn't built or is broken, and on the line of code behind it.
• Sidebar: your plan lines and your prompts, grouped by what malveon found: CONNECTED, BROKEN, NOT BUILT, HALF BUILT, and more. Click any item to jump to it.

Getting started

1. Open your project and click Run check in the Malveon sidebar. If more than one file looks like your plan, malveon asks which one, once.
2. Click Check your prompts too to have malveon check the prompts you type to Claude Code, Codex, Cursor, or Antigravity, not just plan docs. It shows you exactly what it will add to each agent's settings and only writes after you say yes.
3. After that, malveon checks again by itself a few seconds after you save, and whenever a new prompt arrives. Change this with the malveon.autoCheck setting.

New run (the + button, also on the results page) is for starting a new task: one click starts a fresh session, so earlier prompts and changes stop counting, then asks which plan files this run is about and checks. Use it when your agent starts on something new.

Run with build and tests also runs your project's own build, lint, type check and tests. It's a separate button because it runs real commands and can take a few minutes.

Your agent can use it too

The extension connects malveon to your editor's own agent automatically (tested in VS Code; Cursor has its own connection, not yet tested there), so the agent can run the check itself and read the same result you see. For an agent in a terminal or another editor, use Copy setup for another agent in the sidebar menu.

You stay in charge

Anything that changes a setting or stops a prompt from being checked asks you first, in a dialog. The agent can't answer those for you.

The same goes for running a project's own build and test commands: the first time, malveon shows you exactly which commands would run and asks, once per project. A repo you just cloned can't make malveon run its scripts on its own.

Privacy

Malveon runs on your machine and reads your project there. Your code, file names, plans and prompts never leave it; your prompts are saved only in your project, in .malveon/ (ignored by git).

Two things do go over the network:

• Anonymous usage events: which command ran, whether a check came back clean or blocked, your OS and malveon's version. Nothing from your project, and a random ID that isn't tied to you. They follow your editor's telemetry setting: turn telemetry off in VS Code and malveon sends none. DO_NOT_TRACK=1 stops automatic update-network checks; it is not a separate usage-telemetry opt-out.
• An update check once a day, asking whether a newer malveon exists. It sends nothing about you or your project. MALVEON_NO_UPDATE_CHECK=1 turns it off.

License

Free to use during the beta, for personal and commercial work. See the license included with the extension.