caplog

Capture what you did. Remember where you left off. Show up to standup ready.

caplog is a personal developer journaling CLI that passively captures your workday from git commits and manual notes, then uses Claude Code to generate end-of-day summaries and standup updates. All data stays local — SQLite database plus Markdown files.

Install

npm install -g caplog

Requirements

Claude Code must be installed and authenticated (claude available on your PATH). All capture commands (init, repo, sync, note, log) work without it.

Supported platforms: Windows, macOS, Linux.

From source

git clone https://github.com/srimel/caplog.git && cd caplog
npm install && npm run build
npm install -g .

Quick Start

# 1. Initialize caplog (creates ~/.caplog/)
caplog init

# 2. Register the repos you work in
caplog repo add /path/to/my-project
caplog repo add /path/to/another-repo

# 3. Throughout the day: sync commits and add notes
caplog sync
caplog note "Paired with Alice on the auth refactor"
caplog note "Debugged flaky CI — was a race condition in test setup"

# 4. End of day: generate a summary
caplog eod

# 5. Next morning: generate your standup
caplog standup

Commands

caplog init

Create the ~/.caplog/ directory and initialize the database.

caplog repo add <path>

Register a git repository for commit tracking. The path must exist and contain a .git directory.

caplog repo list

Show all registered repositories.

caplog sync

Pull new commits from all registered repos into today's session. Only fetches commits since the last sync. Also writes/updates the daily Markdown log.

caplog note "<text>"

Add a timestamped note to today's session. Auto-creates the session if it doesn't exist yet. Good for meetings, debugging sessions, decisions — anything that isn't a commit.

caplog log [date]

View all captured entries for a given day. Defaults to today. Accepts YYYY-MM-DD format.

caplog log              # today
caplog log 2026-03-25   # specific date

caplog eod

Generate an end-of-day summary using Claude. Produces two sections:

• Summary — What you accomplished (2-5 bullet points)
• Where I Left Off — Context snapshot for tomorrow (last thing worked on, next step, blockers)

The summary is cached in the database, written to ~/.caplog/logs/YYYY-MM-DD.md, and a CONTEXT.md file is placed in your current directory for tools like Claude Code to pick up.

Use --no-context to skip writing CONTEXT.md.

caplog standup

Generate a standup update from yesterday's session. Produces a paste-ready update:

• Yesterday — What was completed
• Today — Planned work (inferred from context)
• Blockers — Any blockers, or "None"

If you ran caplog eod the day before, that summary is included as additional context.

Environment Variables

Data Location

~/.caplog/
  caplog.db              # SQLite database
  logs/
    2026-03-25.md        # Daily Markdown logs
    2026-03-26.md

Daily Markdown files are the primary artifact — readable without caplog installed, searchable with grep, committable to a private repo.

Daily Workflow

During the day:

caplog sync                          # after pushing commits
caplog note "context you want to remember"

End of day:

caplog sync                          # catch any final commits
caplog eod                           # generate summary + context

Next morning:

caplog standup                       # paste-ready standup update

Development

npm run dev          # watch mode (rebuilds on changes)
npm test             # run tests
npm run test:watch   # tests in watch mode
npm run lint         # type-check (tsc --noEmit)
npm run build        # production bundle

See docs/how-it-works.md for a detailed technical walkthrough and docs/contributing.md for architecture and development conventions.

License

MIT