Why a Plain‑Text To‑Do App May Beat Your Fancy Productivity Suite
According to WIRED, Tasks.txt is a free Mac application that lets you manage a to‑do list from a single text document. It strips away the clutter of modern productivity tools and puts your tasks back into a format anyone can read, edit, or move to another program.
The shift matters because most people assume a feature‑rich app is automatically better. In reality, the underlying data model, privacy guarantees, and workflow friction can have a bigger impact on daily productivity than bells and whistles.
The Simplicity of a Single Text File
Tasks.txt stores everything in two plain‑text files: one for the active list and one for the archive. The format follows the todo.txt convention created by Gina Trapani, where each line represents a task and optional tags (e.g., @context, +project) add context without requiring a hidden database. Because the files are human‑readable, you can open them in any editor, search, copy, or pipe them to scripts.
The app splits the visible list into three sections—Next, Backlog, and Done—mirroring a common personal‑productivity method. Next holds the tasks you plan to finish today, Backlog contains everything else, and Done is cleared each morning after the archive moves its entries. This structure forces you to prioritize before you start working, a habit that many complex apps leave to chance.
How Tasks.txt Implements the todo.txt Format
When you type a new line, the app appends it to the active file. A dropdown next to the entry box decides whether the line goes to Next or Backlog. Keyboard shortcuts let you:
- Press Enter to add a task.
- Use Tab to jump from the input box to the list.
- Hit Cmd + Enter to mark a line as complete, which moves it to the Done section.
- Add a note under a task with Enter while the task is selected.
- Reorder items with Cmd + Up/Down.
All actions edit the text file directly, so there is no hidden state. Because the file lives on your Mac, there is no cloud sync, no telemetry, and no account needed. The privacy claim is literal: nothing leaves your machine unless you choose to copy the file elsewhere.
Where It Stands Against Feature‑Heavy Competitors
| Feature | Tasks.txt (plain‑text) | Typical cloud‑based to‑do apps (e.g., Todoist, Microsoft To Do) |
|---|---|---|
| Data storage | Local .txt file, human‑readable |
Remote database, proprietary format |
| Sync across devices | Manual file copy or third‑party sync | Automatic cloud sync |
| Pricing | Free | Free tier, paid premium features |
| Automation | Simple scripts can read/write the file | API access often limited to paid plans |
| Privacy | No telemetry, no servers | Server‑side analytics, optional data sharing |
| Advanced features (recurring tasks, reminders, AI suggestions) | None built‑in; must be added manually | Built‑in, often AI‑driven |
| Learning curve | Minimal; basic keyboard shortcuts | Higher; need to learn app‑specific UI |
The table shows that Tasks.txt wins on privacy, cost, and transparency, while it lags on automatic syncing and out‑of‑the‑box smart features.
The Hidden Trade‑offs No One Mentions
The biggest advantage—having your tasks in a raw text file—also creates the biggest limitation. Because there is no server, you cannot instantly see the same list on a phone or tablet unless you set up a separate sync method such as iCloud Drive or Dropbox. Those services re‑introduce a cloud component, and with it the potential for data leakage or version conflicts.
Another trade‑off is the lack of native reminders. In a typical app, setting a due date triggers a push notification. With Tasks.txt you must rely on the operating system’s calendar or a separate reminder tool, adding a manual step to the workflow.
Finally, the simplicity can be a double‑edged sword for teams. Sharing a plain‑text file via a shared folder works, but there is no built‑in conflict resolution or permission system. If multiple people edit the same file simultaneously, you may end up with duplicate or lost entries. For solo users or very small teams, this is manageable; for larger groups, a cloud service still has an edge.
Getting Started with Tasks.txt Today
- Download the app from the developer’s website and place it in your Applications folder.
- Open Settings and note the file paths for tasks.txt and archive.txt. Keep a backup copy in a folder you sync with your preferred cloud service if you need cross‑device access.
- Create your first list: type a task, choose Next or Backlog from the dropdown, and press Enter.
- Prioritize daily: each morning, move the tasks you plan to complete into Next and clear Done with Cmd + Enter.
- Add context tags (e.g.,
@home +projectX) to enable simple filtering later with the Mac’s search or a custom script. - Automate: write a short shell script that appends overdue items from your calendar to Backlog and run it via a daily cron job.
By following these steps you can replace a cluttered subscription app with a transparent, private list that works entirely offline. If you later discover you need syncing, you already have the file location, making the transition to a cloud folder straightforward.
