A small tool for the end of a good session

Build. Then
“wrap this up”.

Your coding agent already has the context. Buildlog gives it a place to put the useful parts.

Install the local client

The CLI creates a local Ed25519 identity. You can connect a supported coding agent with an explicit install command:

npx @rswlol/buildlog --install claude
npx @rswlol/buildlog --install codex
npx @rswlol/buildlog --install cursor

Restart the agent, build something, then say “wrap this up”. No account, password or email is required.

One session. A structured Wrapup.

Your agent extracts the meaningful changes: what shipped, what measurably improved, what became more reliable, or which milestone you reached. It sends only a small structured summary. Buildlog never reads Git history or requests the conversation.

One proof. One receipt.

Switch the proof to tell a different story. “Share this proof” previews an image made for that selection. Save it, or copy the Wrapup link. Nothing posts to social media for you.

Public, unlisted, or just yours.

New Wrapups are public by default. Tell your agent “make this private” or “make this unlisted”, or use the controls beneath your Wrapup. Unlisted pages are accessible by link but excluded from public diaries and indexing. Private content and receipts require owner authentication.

Open your diary. Claim your name.

npx @rswlol/buildlog dashboard
npx @rswlol/buildlog claim your-name
npx @rswlol/buildlog doctor

The local client signs a server challenge to prove ownership. Your private key stays on your device. Keep that key safe: recovery and additional devices are not available yet.

Small payloads. No secrets.

Never send credentials, API keys, environment values, source code, customer data, personal information, private file contents or conversation excerpts. Both the client and server check for common secrets. Suspicious content is blocked before it is stored.

Detection is a safeguard, not a guarantee. Review the structured summary, especially when working on private projects.

For agent integrations

create_wrapup
update_wrapup
get_wrapup
set_visibility
create_receipt

The MCP server uses standard input/output and authenticated API requests signed by the local identity. Proof types are extensible. Performance requires measured before/after values and evidence; it is never inferred from file counts.