Code Tasks

Turn TODO, FIXME, BUG, and other code comments into a filterable Kanban board, add manual tasks, and hand work to an AI agent.

Code Tasks gives the unfinished work hidden across your source files one place to live. It scans tag comments such as TODO, FIXME, and BUG, turns them into cards, and combines them with manual tasks that are not tied to a comment.

Code Tasks board showing scanned and manual work grouped by tag

Open Code Tasks

  1. Open the project you want to inspect.
  2. Click Tasks in the top toolbar, or choose Navigate → Tasks… from the app menu.
  3. If needed, choose a different project from the Project picker at the top of the dialog.

1DevTool scans when you open Code Tasks. Nothing watches your files in the background, so the feature has no idle performance cost. Click Refresh whenever you want to scan again.

Write Task Comments

Code Tasks recognizes common comment styles across programming and markup languages:

ts
// TODO: handle the empty state
// REVIEW(alex): check the authentication flow
// BUG(#123)!: request can race on a slow network
// FIXME!!: prevent data loss before release

The built-in tags are TODO, FIXME, BUG, HACK, XXX, NOTE, OPTIMIZE, PERF, REVIEW, DEPRECATED, WARNING, and REFACTOR.

  • Put a name in parentheses, such as REVIEW(alex), to record an author or assignee.
  • Put an issue number in parentheses, such as BUG(#123), to attach an issue reference.
  • Add ! for High priority or !! for Critical priority.
  • Keep the description after the colon. The card also includes the file, line number, and nearby source context.

Project ignore rules and common dependency or build directories are skipped, so generated files do not flood the board.

Organize the Board

Use the view switcher to move between the drag-and-drop Board view and the compact List view. You can group tasks by tag, file, author, priority, or source, then sort by priority or file.

The search box matches descriptions, file paths, and assignees. The filter button can narrow the result by priority or by source — Scanned from code versus Manual task. Click a colored tag pill to include or exclude that tag.

Add Manual Tasks

Click Add for work that does not belong in a source comment. Enter a description, tag, and priority, with an optional file, line, and assignee. Manual tasks are saved with the project in .1devtool/manual-tasks.json and appear beside scanned cards.

You can edit, delete, or drag a manual card. When the board is grouped by tag, priority, or author, dropping the card in another column updates that field. Scanned cards cannot be dragged because the source comment is the record of truth; edit the comment and click Refresh instead.

Act on a Task

Select a card to open its details and surrounding code. From there you can:

  • Open in Editor to jump to the exact file and line.
  • Send to Agent to create a fix prompt containing the tag, location, description, and source context.
  • Copy as Markdown to paste a checklist item into GitHub, Linear, Notion, or a document.

For manual tasks, the same detail panel also provides Edit Task and Delete Task.

Configure Tags and Scanning

Click the gear button in Code Tasks to enable or disable built-in tags, add custom tags, change tag colors, choose a default grouping, or extend the ignore list. These settings are saved to .1devtool/tasks.json, so the project can keep a consistent task vocabulary.

Related