Simple pricing

Start free. Turn on full automation when you're ready.

Scan a repo for free with Hobby, or connect a repo permanently with Pro and CodeMD.dev finds and runs the right tests, writes the ones you're missing, and files and resolves real bugs on every commit.

Free

Hobby

For a quick, one-time look at a repo.

$0 / month
Analyze a repo free
  • ✓ Paste a GitHub URL. Drop in any repo — the dashboard shows github.com/medusajs/dtc-starter as a sample by default; replace it with your own when you're ready.
  • ✓ Or upload a code archive. No GitHub connection required — zip up your code and analyze it directly.
  • ✓ Free VS Code CODE.md plugin. Callgraph search, impact analysis, and test discovery, right in your editor.
  • ✓ On-demand scans. Run an analysis whenever you want, at no cost — no recurring, per-commit automation.

No credit card required.

Full automation

Pro

Call-graph Test Management System

$19.99 / month, per repo
Start free trial
  • ✓ Everything in Hobby, plus:
  • ✓ Full online repo scanning for large repos. Connect a repo once and CodeMD.dev keeps its callgraph current as it grows.
  • ✓ Finds and runs the relevant tests on every commit. Automatically — no manual scan needed.
  • ✓ Creates and runs any missing tests. Mechanically from a real caller when possible, or with an AI coding agent when it isn't.
  • ✓ Bug management. Every real failure is filed as a tracked bug with the exact commit, function, and test that broke.
  • ✓ Auto-fixes and resolves bugs. Claude or Codex fixes the code and re-runs the test to confirm the fix, for every commit.

14-day free trial, no credit card required. Cancel anytime.

Frequently asked

What's the difference between Hobby and Pro?

Hobby is a free, on-demand scan — paste a GitHub URL or upload an archive whenever you want to look at a repo, plus the free VS Code plugin. Pro connects a repo permanently and runs the full loop automatically on every commit: finding and running tests, generating missing ones, and filing and resolving bugs.

What counts as a "repo" for Pro billing?

Any repository you connect through the dashboard for automatic, per-commit scanning. Each connected repo runs the full loop — discovery, generation, execution, and bug filing — independently.

How are missing tests generated?

CodeMD.dev prefers a mechanical regression test built from a real caller in your callgraph. When that isn't possible, it hands the gap to Claude or Codex to write one.

Is a pass ever just an AI's self-report?

No. Every pass/fail is a real test-runner exit code, and generated tests are coverage-confirmed to have actually exercised the changed lines.