My agent made 40 decisions today and wrote down zero. So I built dlog

Description and use

dlog lets developers quickly log decisions made by coding agents, storing them in a JSONL file for later search and handover.

Problem

Coding agents make dozens of decisions per session but never record them, leading to repeated debates and wasted time in subsequent sessions.

Outcome

dlog enables developers to capture the rationale behind each decision in seconds, preventing redundant debates and improving knowledge transfer between sessions.

Workflow

• 1. Run coding agent and make a decision.
• 2. Immediately execute dlog add "decision title" -r "reason" -t tag1,tag2 to record the choice.
• 3. Use dlog list to view recent decisions or dlog search to find past ones.
• 4. Export decisions to Markdown with dlog export-md for inclusion in handover documents.
• 5. Optionally use --global to log decisions across projects in ~/.dlog.jsonl.
• 6. Install dlog via a single curl command and make it executable.

Evidence

Coding agents make dozens of decisions per session — which library, which schema, which approach — and never write them down.

Source

dlog is the 30-second habit that fixes this. One line when you decide something:

Source

Each entry records the timestamp, title, reason, tags, working directory, and the git commit sha (or null outside a repo).

Source

Install — it's one stdlib-only file, no dependencies, no network, no accounts:

Source