# tnotes for…

Concrete setups for the people who actually use terminal notes: the config, the daily loop, and what tnotes deliberately leaves to other tools.

• tnotes for AI agentsGive Claude Code, Codex or any AI agent a notes vault it can read and write through a JSON CLI, with conflict copies instead of silent overwrites.
• tnotes for vim usersTerminal Markdown notes for vim users - j/k, gg/G, i/a/o, u and dot-repeat in a TUI, with plain files you can still open in real vim any time.
• tnotes for Obsidian usersOpen your Obsidian vault in the terminal with tnotes: same folders, [[wikilinks]] and #tags, no plugins, canvas or properties. Run both on one directory.
• tnotes for sysadminsRunbooks and incident notes for sysadmins over ssh - a static musl binary, tmux-friendly TUI, --dir per host, and append from scripts to log what you did.
• tnotes for dotfiles peopleKeep the tnotes config.toml in your dotfiles repo, set roots per machine, and put the vault in git with .Trash ignored: a reproducible notes setup.
• tnotes for ZettelkastenA terminal Zettelkasten with title-based [[links]], a backlinks overlay, nested #tags and CLI capture, plus an honest note on what it lacks: IDs, graph view.