Skip to content
gournal

A Developer's Command-Line Journal with Git Integration

You and your AI agents log finished work in one local journal. Gournal links each entry to its pull requests and commits, and it writes your standup from them.

npm install -g gournal

Needs Node 22.13 or newer. The gh CLI is optional.

gournal standup on sample data. Two projects, a merged pull request folded under the entry it belongs to, and an Also line for GitHub items not linked to a done entry in the report. Read the standup as text.

What gournal does

tools/call add_entry
"summary": "Wrote retry tests",
  "project": "worker",
  "agent": "claude-code" 

Agents log for you

Claude Code and other MCP clients add entries through the gournal MCP server as they finish work.gournal setup claude registers the server and installs the skill. An optional Stop hook reminds Claude to log.

Logging with AI agents
Blockers
  Nov 14  Waiting on keys  [api]

Next
  Nov 15  Ship metrics  [worker]

Standups that write themselves

gournal standup groups today's done entries by project. Open blockers and next items carry forward until an entry resolves them. Ask for --yesterday, --week, or a date range.

Standups and work logs
10:41  Fixed token refresh race
       ↳ merged #412
       ↳ 3 commits

GitHub, linked

gournal sync reads your pull requests, commits, and reviews through the gh CLI. It links each item to an entry by PR number, commit sha, or branch and time. Items not linked to a done entry in the report go to the Also line.

GitHub activity

How it works

Pick a step to mark the lines it makes in the standup.

Standup: Today (2026-11-15)   Done  api  10:41  Fixed the token refresh race         ↳ merged #412 Fix token refresh race         ↳ 3 commits   worker  14:04  Added retry with backoff to webhooks         ↳ 2 commits  16:09  Wrote tests for the retry policy   Blockers    Nov 14  DFKD4PX0  Waiting on staging keys  [api]   Next    Nov 15  9BZNA94G  Ship retry metrics  [worker]   Also: 1 commit, 1 PR merged, 1 review in 2 repos (--activity to expand)    merged    acme/docs#57  Document webhook retries    reviewed  octo/web#88   Dark mode tokens
The standup from the recording, as text. Sample data: acme and octo are made-up GitHub owners. Your agent logged the marked lines in step 1.

~/.gournal/gournal.db

One SQLite database file holds every entry and every synced activity item. Set GOURNAL_HOME to keep it somewhere else. gh keeps your GitHub login, not gournal.

Local-first. SQLite on your machine. No account, no tokens stored.