The build log: build in the open without writing a post
You already tell the story of your product every day, to your coding agent. The build log keeps the moments worth sharing, you choose which ones go out, and Borker turns them into a running log of posts in the order it happened, from Day 1 on.
Building in the open works when you post often, and posting often is the part that slips when you are building. The build log takes the story you already tell your coding agent every day and turns it into posts, with you choosing what goes out.
Your working sessions become a running log of posts
The build log keeps four kinds of moment: a Finding, a Decision, something you Shipped, and a Reversal, often the best story of all. Each one becomes a post, and the posts run in the order it happened, counted from Day 1.
From your sessions to your posts
Only the entries you keep are sent to Borker.
852 feet in 59 seconds
Written a few hours before it goes out
For the papers: four flights today, the longest 852 feet in 59 seconds.
The paper says three miles over the ocean
Written a few hours before it goes out
The paper says three miles over the ocean. It was 852 feet over sand, and it was enough.
852 feet in 59 seconds
For the papers: four flights today, the longest 852 feet in 59 seconds.
The paper says three miles over the ocean
The paper says three miles over the ocean. It was 852 feet over sand, and it was enough.
852 feet in 59 seconds
The paper says three miles over the ocean
For the papers: four flights today, the longest 852 feet in 59 seconds.
The paper says three miles over the ocean. It was 852 feet over sand, and it was enough.
Read it as steps
- On your machine, the skill reads your working sessions with your coding agent.
- The skill removes the keys, emails, wallets and pasted blocks it recognizes before anything is read.
- In your browser, the review page shows the entries worth sharing. Tick the ones to keep, edit any title or text, and leave the rest.
- Press Send, and the entries you ticked go to Borker. Nothing else is sent to Borker.
- In Borker they arrive on the Build log tab as Not yet planned. With New entries: Borker paces them, Borker plans each one, oldest first, as a planned post in Planning. Nothing is written yet.
- Borker writes each post a few hours before it goes out, and its card reads "From your build log: Day N". It waits in Posts as Needs you, unless its voice is set to Publish on their own.
How it works for you
- Create an agent key with write access under Settings → Keys.
- Install the build log skill in your coding agent. The skill page has the one line to paste and the current version.
- Run
/borker-build-login any session. It reads your recent sessions in that project, writes each moment as an entry in your own words, and asks how you want to review: in the browser, in the terminal, or skip. - Keep the entries you want and press Send. Only those leave your machine.
Keys, emails, wallets and pasted blocks are taken out before anything is read. The review page marks every name left in an entry, and one click removes it. Send refuses an entry that still carries an email address, a key or a wallet address.
From entry to post
Your entries arrive on the Build log tab of the Sources page. Borker plans them oldest first, onto the next days your channels post, or you plan them yourself with Plan it. Each post is written a few hours before it goes out, from your own account of what happened, in the voice of the channel it goes to. Its card reads "From your build log: Day N", and it waits for you in Review like every other post, unless its voice publishes on its own.
Read the full guide at Build log.
New here? Borker is the AI content engine for founders.
We learn your voice, read your sources, plan your week and write each post before it goes out, while you build the actual product.