Skip to Content
BorkerBorker Docs
Changelog

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.

Shipped October 24, 2026
Try Borker

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.

Your machineYour sessions
Your browserReview before it goes to Borker
Borker
Removed before reading
2 of 3 tickedSend 2 to Borker
PlanningBorker plans each one
PostsBorker writes each one
[key]
Shipped852 feet in 59 seconds
◌ 13:10Planned

852 feet in 59 seconds

Written a few hours before it goes out

PersonalFrom your build log: Day 4
13:10Needs you

For the papers: four flights today, the longest 852 feet in 59 seconds.

PersonalFrom your build log: Day 4
[wallet]
FindingThe paper says three miles over the ocean
◌ 09:00Planned

The paper says three miles over the ocean

Written a few hours before it goes out

PersonalFrom your build log: Day 5
09:00Needs you

The paper says three miles over the ocean. It was 852 feet over sand, and it was enough.

PersonalFrom your build log: Day 5
[email]
FindingA letter from a friend
Nothing else is sent to Borker.
Your machineYour sessions
Removed before reading
Your browserReview before it goes to Borker
2 of 3 tickedSend 2 to Borker
Borker
PlanningBorker plans each one
Nothing is written yet.
PostsBorker writes each one
Written a few hours before it goes out
[key]
Shipped852 feet in 59 seconds
◌ 13:10Planned

852 feet in 59 seconds

13:10Needs you

For the papers: four flights today, the longest 852 feet in 59 seconds.

PersonalFrom your build log: Day 4
[wallet]
FindingThe paper says three miles over the ocean
◌ 09:00Planned

The paper says three miles over the ocean

09:00Needs you

The paper says three miles over the ocean. It was 852 feet over sand, and it was enough.

PersonalFrom your build log: Day 5
[email]
FindingA letter from a friend
Nothing else is sent to Borker.
Your machineYour sessions
[key]
[wallet]
[email]
Removed before reading
Your browserReview before it goes to Borker
2 of 3 tickedSend 2 to Borker
Shipped852 feet in 59 seconds
FindingThe paper says three miles over the ocean
FindingA letter from a friend
Nothing else is sent to Borker.
Borker
PlanningBorker plans each one
◌ 13:10Planned

852 feet in 59 seconds

◌ 09:00Planned

The paper says three miles over the ocean

PostsBorker writes each one
13:10Needs you

For the papers: four flights today, the longest 852 feet in 59 seconds.

PersonalFrom your build log: Day 4
09:00Needs you

The paper says three miles over the ocean. It was 852 feet over sand, and it was enough.

PersonalFrom your build log: Day 5
Borker does itYou do it
Read it as steps
  1. On your machine, the skill reads your working sessions with your coding agent.
  2. The skill removes the keys, emails, wallets and pasted blocks it recognizes before anything is read.
  3. 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.
  4. Press Send, and the entries you ticked go to Borker. Nothing else is sent to Borker.
  5. 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.
  6. 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

  1. Create an agent key with write access under Settings → Keys.
  2. Install the build log skill in your coding agent. The skill page has the one line to paste and the current version.
  3. Run /borker-build-log in 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.
  4. 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.

On this page