Terminal Task Manager working title

The problem

Developer task lists die in other apps. The work happens in a terminal and an editor; the plan lives in a browser tab. Every context switch to the tracker costs a little, so tasks get captured late, vaguely, or never — and a week later the list describes work that no longer matches the codebase.

The research question

Why do developer task lists decay? Our working hypothesis: tasks lose value when they lose context — the branch, the failing command, the file you were staring at when you realized the work existed. What happens if the task system lives where that context already is?

Why existing approaches are insufficient

Issue trackers are built for coordination between people, not for the private queue of a person mid-flow. They ask for titles, labels, and projects at exactly the moment the developer wants to type five words and get back to the error message. TODO comments capture location but have no lifecycle. Both lose the session — what you were doing, what you had just run.

The product

A terminal-native task tool: capture a task in one line without leaving the shell, and it keeps its context — the repository, the directory, optionally the last command or a file reference. Come back tomorrow and the task can put you back where the work was, instead of describing it from memory.

Development status

This is an experimental tool — an internal experiment that changes shape frequently and is not distributed yet. The capability list above describes what the experiment is exploring, not a released feature set. If it earns its keep in daily use, an open-source release is the likely path; we will not call it open source until a public repository actually exists.

What this project demonstrates

Small tools are honest tests of product judgment: every keystroke of friction is visible. This project demonstrates DataKnife’s approach to developer experience, local-first design, and the same context-preservation ideas that run through our larger systems.