tdo

Fast & Simple Note Taking! 📃🚀

tdo in action

tdo is a opinionated, command line based note-taking system. Demo video

• Unified Note System: Manage daily todos, journal entries, and long-term notes in one organized system with intuitive navigation
• Natural Language Dates: Use expressions like tomorrow, next-friday, 2-weeks-ago, or 2025-12-25 instead of calculating offsets manually
• Fuzzy Search: Interactive search powered by fzf with syntax highlighting to quickly find and review any note
• Git Integration: Automatically commits and backs up your notes with timestamps for seamless sync across devices
• Editor Flexibility: Works with any editor through $EDITOR - vim, emacs, vscode, includes neovim integration
• AI & Automation: Integrates with workflows, pipes, subshells, and AI agents through mcp-tdo

• ripgrep, fzf
• bat (optional, for syntax highlighting in search)
• coreutils (required on macOS, for gdate command)

git clone https://github.com/2kabhishek/tdo
cd tdo
./install.sh

• NOTES_DIR should point to your notes directory

• TODOS_DIR optional, should point to your todos directory, default: NOTES_DIR/todos

• JOURNAL_DIR optional, should point to your journal directory, default: NOTES_DIR/entries

• EDITOR set to your choice of editor

If you want to customize the setup or are facing issues with installation, you can set up tdo manually.

Change these commands according to your needs.

# Link tdo to a directory that's in PATH (~/.local/bin here)
ln -sfnv "$PWD/tdo.sh" ~/.local/bin/tdo
# Create a notes dir if not already present
mkdir -p $HOME/Projects/Notes
# Add the NOTES_DIR env var to your shell config ~/.bashrc, ~/.zshrc etc
echo "NOTES_DIR=$HOME/Projects/Notes" >> ~/.zshrc
# Add sample templates to your NOTES_DIR
cp -irv templates $NOTES_DIR
# Reload shell config
source ~/.zshrc

If you want to enable tab completion for tdo, add this to your shell's RC file (bashrc, zshrc, config.fish etc).

# zsh and bash
source /path/to/tdo/completions/tdo_completion.sh
# fish
source /path/to/tdo/completions/tdo_completion.fish

This will allow you to use tab completion to quickly access your notes when you type tdo <tab>.

If you want to sync your notes across devices, you can set up a git repo on the $NOTES_DIR and add GitHub/GitLab as remote.

cd $NOTES_DIR
git init
git add .
git commit -m 'init: notes'
git remote add origin <your-remote-git-url>
git push origin main

tdo will automatically commit every change with a timestamp like 03 Feb 11:33 as commit message.

If you use Neovim, I highly recommend using tdo.nvim, it seamlessly integrates tdo and nvim and adds some useful features on top.

• tdo to open today's todos
• tdo <date_expression> to open todos with flexible date formats, e.g: tdo 1, tdo monday, tdo next-friday, tdo 2-weeks-later, tdo 2025-07-14
• tdo entry <date_expression> to open journal entry with same flexible date formats as todos, e.g: tdo e tomorrow tdo e last-tue, tdo e 1-year-ago
• tdo <note_title> to open or create a note_tile.md note, use folder names to categorise notes, e.g: tdo tech/vim-tips
• tdo note or tdo n to create a new note with the current timestamp in drafts
• tdo find <text> or tdo f to interactively search for text in all your notes
• tdo find without any search term to review all your notes
• tdo todo or tdo t to show all your pending todos
• tdo pending or tdo p will show count of pending todos
• tdo commit <path> or tdo c to commit changes in path, happens automatically, needed for plugins and integrations

Run tdo h to get more help info on the command line

tdo supports intuitive natural language date expressions for both todos and journal entries. This makes it easy to reference dates without calculating offsets manually.

Numeric Offsets:

• Positive numbers for future days: 1, 7, 30
• Negative numbers for past days: -1, -7, -30

Basic Relative Dates:

• today, tomorrow, yesterday

Weekdays:

• sunday, monday, tuesday, wednesday, thursday, friday, saturday
• next-sunday, next-monday, etc. (next week's occurrence)
• last-sunday, last-monday, etc. (previous week's occurrence)
• Short forms: sun, mon, tue, wed, thu, fri, sat next-sun, last-mon, etc.

Quick Aliases:

• next-week, last-week, next-month, last-month, next-year, last-year

Programmatic Patterns:

• N-weeks-ago / N-weeks-later (e.g., 2-weeks-ago, 3-weeks-later)
• N-months-ago / N-months-later (e.g., 1-month-ago, 6-months-later)
• N-years-ago / N-years-later (e.g., 1-year-ago, 2-years-later)

Absolute Dates:

• YYYY-MM-DD format (e.g., 2025-07-14)

tdo expects an opinionated directory structure to function.

• Notes live in the notes sub-dir, use these for long term knowledge management, second brain
• Notes use the templates/note.md file as template
• Todos live in the todos sub-dir, use these for short term notes, daily todos
• Todos use the templates/todo.md file as template
• Journal entries live in entries sub-dir, use these for personal notes, life logging
• Journal entries use the templates/entry.md file as template

├── todos
│   └── 2023
│       └── 11
│           └── 2023-11-29.md
├── entries
│   └── 2024
│       └── 02
│           └── 2024-02-03.md
│── notes
│   └── tech
│       └── quit-vim.md
│       └── arch-btw.md
└── templates
    ├── entry.md
    └── note.md
    └── todo.md

You can configure tdo by either defining environment variables or via a $HOME/.config/tdorc file.

• ADD_ENTRY_TIMESTAMP [boolean]: Whether to add a time stamp when using tdo entry or tdo e.
• ADD_NEW_NOTE_TIMESTAMP [boolean]: Whether to add a time stamp when creating new notes with tdo <note_title>.
• FILE_NAME_AS_TITLE [boolean]: Whether to add the file name as title when creating new notes with tdo <note_title>. If true, then it adds <note_title> as a markdown title in the first line of the new note.
• ENTRY_TIMESTAMP_FORMAT [string]: can be any bash string such as a date format expression. It is ignored if ADD_ENTRY_TIMESTAMP is set to false.
• NOTE_TIMESTAMP_FORMAT([string]: can be any bash string such as a date format expression. It is ignored if ADD_NEW_NOTE_TIMESTAMP is set to false.

ADD_ENTRY_TIMESTAMP=true
ADD_NEW_NOTE_TIMESTAMP=false
FILE_NAME_AS_TITLE=false
# Reads ## Mon, 12:00 PM
ENTRY_TIMESTAMP_FORMAT="## %a, %I:%M %p"
# Reads ## Fri. Apr 06, 2024 - 06:48 PM
NOTE_TIMESTAMP_FORMAT="## %a. %b %d, %Y - %I:%M %p"

configs defined in tdorc will override corresponding environment variables

tdo includes comprehensive unit and integration tests to ensure reliability.

# Install bats-core (testing framework)
brew install bats-core  # macOS
sudo apt-get install bats  # Ubuntu/Debian

# Run all tests
bats tests/unit tests/integration

• Unit Tests: Date parsing, file generation, utility functions
• Integration Tests: End-to-end workflows for todos, journal entries, and notes
• Mock System: Isolated testing with fixed dates and mocked external dependencies

All tests use a comprehensive mocking strategy to ensure consistent, predictable results across different environments and dates.

You tell me!

After trying out every note management system under the sun I had decided on using plain markdown notes powered by nvim2k.

tdo is a spiritual successor and complimentary tool to that, taking the same principles and making it more accessible and simple.

• cmtr — Fast git commits
• mkrepo — Spin up new GitHub repos from the CLI
• ghpm — Manage all your GitHub repos
• gsync — Sync your git repos

• dots2k — Dev Environment
• nvim2k — Personalized Editor
• sway2k — Desktop Environment
• qute2k — Personalized Browser