New: watch your coding agents work, step by step, on a live board. Try the demo, no account

Free tools

Extract TODO comments from code

Paste code or drop a project folder and this page lists every TODO, FIXME, HACK, XXX and BUG comment with its file name and line number. Copy the result as a Markdown checklist, JSON or CSV.

Runs in your browser. Pasted code and dropped files are read on this page and never uploaded. By Jake Marsh.

Drop a folder or files here

node_modules, .git, build folders, images and lockfiles are skipped. Files stay on this device.

Comments in //, /* */, #, --, <!-- --> and triple-quote styles are recognised.
Markers to find

Nothing to scan yet. Paste code, load the example or drop a folder.

How to use it

  1. Drop a project folder on the box, or use Choose a folder. You can also paste one file into the text area, or load the example.
  2. Tick the markers you care about. TODO, FIXME, HACK, XXX and BUG are on by default; OPTIMIZE and NOTE are optional.
  3. Check the count line to see how many files were scanned and skipped. Vendored folders, binaries and lockfiles are left out.
  4. Pick Markdown checklist, JSON or CSV, then copy the list or download it.

What counts as a TODO comment

A marker counts when it is the first word of a comment, so a string like "TODO list", a URL ending in #TODO and a sentence such as "// see the TODO in auth.ts" are all left out. The extractor recognises //, /* */, a leading * in doc blocks, #, --, <!-- -->, ;, % and triple quotes, and follows /* */ and <!-- --> comments across lines, so a TODO on the third line of a doc block is found too.

Owner tags in parentheses are kept: TODO(sam): handle expired cards becomes owner sam and text handle expired cards. Matching is case sensitive unless you tick lowercase too.

// TODO(sam): handle expired cards before we retry
/* FIXME: retries double-charge when the webhook is slow */
x = run()  # HACK: skips the idempotency key in test mode
Three comments it finds

What it skips

  • Folders named node_modules, .git, dist, build, .next, vendor, target, venv and coverage.
  • Images, fonts, archives, compiled files, source maps and lockfiles.
  • Files over 1 MB, files with binary content, and lines over 2,000 characters such as minified bundles.
  • Anything past 5,000 results, so a huge repo cannot freeze the tab.

Questions

Does it upload my code?
No. Files are read in your browser tab with the File API and scanned there. The page makes no network request with your code, so it also works offline once loaded.
Can it scan a whole repo?
Yes. Drop the folder or use Choose a folder. Vendored and build directories, binaries and lockfiles are skipped, and the count line tells you how many files were scanned and how many were left out.
Why did it miss a TODO I can see?
The marker has to open the comment (an @ in front, as in @todo, is fine) and stand as its own word, so TODOS or TODO_LIST do not count. Lowercase todo needs the Match lowercase too option, and OPTIMIZE or NOTE need their boxes ticked. Text in a Markdown paragraph or a string is not a code comment, and lines over 2,000 characters are skipped.
Is the CSV safe to open in a spreadsheet?
Yes. Cells that start with =, +, - or @ get a leading apostrophe so a comment cannot run as a formula, and commas and quotes are escaped.
Does it find who wrote each TODO or when?
It reads the owner in TODO(name) when the author wrote one. It cannot see git history from a browser, so for authors and dates run git blame on the file and line it lists.

Turn the list into tasks your agent picks up

A checklist in a README goes stale. Taskhold files each TODO as a task with its file and line through the taskhold_create_from_todo tool, so Claude Code, Cursor or Codex can pick it up from one shared list. The guide to turning code TODOs into tasks shows the one line to add to your agent's instructions.

Or connect your agent first, no sign-up: add https://taskhold.com/api/mcp as an MCP server. The first time it uses Taskhold, it gives you the trial link.

Related tools

  • Conventional commit message builder

    Fill in type, scope, description and breaking change, and get a commit message checked against the Conventional Commits spec. Paste an existing one to validate it.

  • CLAUDE.md and AGENTS.md generator

    Answer a few questions about your repo (stack, commands, rules, do-nots) and get a starter CLAUDE.md and AGENTS.md, either as one shared file or as two.

  • Coding agent visibility check

    Eight yes-or-no questions about the moments that cost time when agents run unattended. Each no comes back with the gap, the fix and a guide.

All free tools