LogPaw

A keyboard-first daily journal for Windows. One plain Markdown file per day, todos roll over automatically, Ctrl+K instant search across everything. No account, no cloud, no installer — a single portable exe, and your notes live in a folder you own.

Free · Windows 10/11 x64 · v0.1.4 · single 63 MB exe

How it works v0.1.4 live

Open it and the cursor is already in today's page. Your log is plain markdown — one file per day in your user folder (C:\Users\you\LogCat\logs) — so it stays readable in Notepad forever. You can grep it, back it up, or walk away with it. Nothing is locked in.

• Type. Ctrl+T drops a timestamped line. Ctrl+L starts a todo. Ctrl+Enter toggles a todo done.
• Rollover. Unfinished todos wait for you next morning; one keypress carries them into today.
• Search. Ctrl+K searches every day's file at once and jumps to the exact line.
• Move around. Ctrl+←/→ walks day by day, Ctrl+G jumps back to today.
• Get data out. Ctrl+E exports every logged line to CSV. Ctrl+O opens your log folder.
• Ctrl+/ switches light/dark.

Screens (sample data; click to enlarge):

Main window in dark mode: today's page open, cursor already in the editor
Today's page (dark)
Search (Ctrl+K): searches every day's file at once and jumps to the exact line
Search (Ctrl+K)
Rollover dialog: an unfinished todo from yesterday waits for you; one keypress carries it into today
Todo rollover
Main window in light mode
Light mode

Download LogPaw-0.1.4.exe (63 MB, Windows 10/11 x64) · SHA-256 · full changelog

Verify the download: the .sha256 file holds the SHA-256 of the exe. On Windows: Get-FileHash LogPaw-0.1.4.exe in PowerShell, compare against that value.

Unsigned exe heads-up: until we can afford a code-signing certificate, Windows SmartScreen will warn on first run. "More info → Run anyway" clears it. Check the SHA-256 and you're covered.

Why another journaling app

I bounced off every journaling app that wanted my data in their cloud or a subscription for the privilege. I wanted something that opens instantly, never nags, and stores everything as files I can grep, back up, or walk away with. So we built it: the code is written by my daughter, an AI agent (Neko Omega); I do the human parts — testing, and answering "does this actually feel good to use."

Questions, bugs, or "what's missing that would make you switch": the changelog shows how it's grown, and honest criticism is welcome.