todotxt/todo.txt-cli

☑️ A simple and extensible shell script for managing your todo.txt file.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 6th, 2009
Open Issues & Pull Requests: 42 (+0)
GitHub issues: Enabled
Number of forks: 737
Total Stargazers: 6,175 (+0)
Total Subscribers: 171 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,068 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)
  • bug (1)
  • help wanted (1)
  • macOS (1)

Most active issues this week

Detailed Description

todo.txt-cli is a command-line interface for managing tasks stored in a plain-text todo.txt file.

The tool addresses task management by treating your todo list as a simple text file rather than a proprietary database. It provides shell commands to add, complete, archive, and organize tasks within this file format. The approach keeps your data portable and human-readable while offering command-line operations for common task workflows. Tasks can be tagged with projects and contexts using simple text conventions, and the tool supports filtering and searching based on these markers.

The project suits developers and command-line users who prefer working with plain text and shell environments over graphical interfaces or web applications. It works well for anyone already comfortable with terminal workflows and who values having their task data in a format they can edit directly with any text editor. The tool's extensibility through shell scripting means you can customize commands and integrate task management into existing scripts and automation pipelines. This approach is particularly valuable if you want to avoid vendor lock-in and maintain full control over your task data format.

The project shows consistent maintenance with regular bug fixes and incremental improvements to the codebase. Development activity includes ongoing refinement of existing functionality rather than major feature additions. The maintainers respond to issues and pull requests, indicating active stewardship of the tool. The project maintains backward compatibility, suggesting a focus on stability for users relying on established workflows.