---
title: "Guides · tnotes"
description: "Long-form guides on terminal note-taking, Markdown wikilinks, plain-text sync and encryption, and giving AI coding agents a notes memory."
canonical: https://tnotes.app/guides
---

# \# Guides

Editorial, tool-agnostic pieces. tnotes shows up where it fits; the rest is about the approach.

-   [Terminal note-taking in 2026: four approaches and how to pick oneEditor plus grep, CLI tools like nb and jrnl, TUI apps, or editor plugins like vimwiki and org-mode: tradeoffs, a decision table, and a minimal setup for each.](/guides/terminal-note-taking)
-   [Markdown wikilinks in the terminal: resolution, backlinks, renamesHow \[\[wikilinks\]\] resolve by filename, title or id in Obsidian, vimwiki, Logseq, Zettlr, Dendron and tnotes; backlinks, rename handling, and ripgrep recipes.](/guides/markdown-wikilinks-terminal)
-   [Persistent memory for Claude Code from a Markdown notes folderGive a coding agent durable memory from a Markdown notes folder: the CLI loop, an AGENTS.md snippet, overwrite safety, and the alternatives stated fairly.](/guides/notes-memory-for-claude-code)
-   [Syncing plain-text notes: git vs Syncthing vs iCloud vs Dropboxgit, Syncthing, iCloud Drive and Dropbox for a Markdown notes folder: conflict files, atomic writes, junk entries, and encryption via gocryptfs, fscrypt or age.](/guides/plain-text-notes-sync)
