FAQ

Where are my entries stored?

As individual Markdown files in journal_dir (default ~/.driftlog). One file per entry, named by date and a slug of the title. Tags are stored inline as #hashtags and in a small YAML front-matter block.

Does it sync to the cloud?

No, and that's deliberate. driftlog has no server and no account. If you want sync, point journal_dir at a folder you already sync (Syncthing, a git repo, Dropbox, etc.). Plain files make this trivial.

Is there a database?

Only a disposable search index under ~/.cache/driftlog. Delete it anytime; driftlog reindex rebuilds it from your files. Your data is always just the Markdown.

Can I encrypt my journal?

Yes. Set [encryption] enabled = true with the age or gpg backend and a recipient. Entry bodies are encrypted at rest; driftlog decrypts on read using your key.

Which editors work?

Any editor that can be told to block until the file closes: nvim, vim, hx, nano, emacs, code --wait, zed --wait. Set it via editor or $EDITOR.

How is this different from a notes app?

driftlog is intentionally tiny and append-oriented — it's a log, not a wiki. No GUI, no plugins, no sync service. If you live in the terminal and want frictionless timestamped entries you fully own, it fits. If you want backlinks and a graph view, you want something bigger.

Windows?

Yes — there's a native driftlog.exe. Paths and $EDITOR behave as you'd expect under PowerShell and WSL.

How do I contribute or report a bug?

driftlog is MIT-licensed free software — bug reports with a minimal reproduction and small, focused patches are both welcome. See About for how the project is run.