Code Tasks (Replaced)

TODO-comment scanning was removed in v1.53. Here is what replaced it, and what happened to the tasks you already had.

This feature was removed in v1.53.0. The Tasks button no longer scans your code for TODO / FIXME comments — it opens the Tasks board instead. This page explains the change and where your old tasks went.

What Code Tasks used to do

Code Tasks scanned your source files for tag comments — TODO, FIXME, BUG, HACK, NOTE — and turned each one into a card on a board, alongside manual tasks you typed in yourself.

It was a read-only view of your comments. Every open produced the same cards again from the same comments, and nothing about a card survived except the comment it came from.

Why it was removed, not upgraded

Scanned tasks were re-derived on every open and never durable. You could not assign one, an agent could not work one, and a note you added to a card disappeared the next time the scan ran. The new Tasks board is built on the opposite premise: a task is a real markdown file in your repository that diffs, reviews, and travels with a branch.

Both things could not be true of the same board, so scanning went.

What replaced it

Capture from where the problem appears — select a stack trace in a terminal, or a few lines in the editor, right-click, and choose Add task. The task keeps a reference back to the file and line it came from. This is the direct replacement for "I found something while reading code and want to write it down."

Decompose a goal — describe an outcome and an agent proposes a task set for you to edit and accept. Nothing is written until you accept it.

Assignment that dispatches — picking a target spawns the terminal, sends the task, and binds the run to the card. This is what a scanned comment could never do.

What happened to your tasks

Your manual tasks were migrated, not lost. On the first open of a project, .1devtool/manual-tasks.json becomes one markdown task per entry:

  • description → title
  • priority mapped across
  • tag kept as a label
  • file / line kept as a reference

The old files are renamed *.v1.bak and never deleted, so nothing is destroyed by the migration.

Tasks that only ever came from scanning are not migrated. They were re-derived on every open and were never durable — there was no state to carry forward.

If you still want a TODO list

Your comments are still in your code, and grep/rg still finds them. If tag comments are how you like to work, keep writing them — and use right-click Add task on the ones that deserve to become real work items with an owner and a history.

Related