Buildlog turns context from a coding agent into a development diary and shareable proof. It is for developers who want to keep a readable record of the work they ship and explain it to other people.
What does buildlog do?
A coding agent already has context about the work being done. Buildlog’s purpose is to turn that context into a record of what changed, why it matters and what can be shared. The development diary gives the work a place to be read beyond the coding session.
What are Wrapups and Receipts?
A Wrapup records one coding session. A Receipt turns one selected proof from that session into a shareable image. Together, the sessions form a development diary. A receipt can be saved as a PNG; it does not automatically post to social media.
Wrapups can be public, unlisted or private, with new entries defaulting to public. Choose the visibility that fits what you want to share.
Which coding agents does it target?
The client includes MCP setup for Claude Code, Codex and Cursor. It accepts a concise structured session summary, without uploading the full conversation or collecting Git history. The npm package is still coming soon.
From coding context to a development diary
The workflow starts with a summary of the coding session, then produces a diary entry and a receipt for selected evidence. Performance receipts require measured before-and-after values and supporting evidence. Buildlog does not independently verify a benchmark.
The diagram above illustrates the flow; its example output is illustrative. The buildlog documentation explains the workflow, visibility options and client setup.
Where can I try buildlog?
Visit build.rsw.lol for the product. The npm package is coming soon; the command below is a preview and is not yet available to install.
npx @rswlol/buildlog