Skip to Content
BorkerBorker Docs
Sources

Build log

Your working sessions with your coding agent become a running log of posts, in the order it happened, day by day.

Build in the open without writing. You already tell the story of your product every day, to your coding agent: what you found, what you decided, what you shipped, what you undid. The build log keeps the moments worth sharing, you choose which go out, and Borker turns them into a running log of posts in the order it happened, from Day 1 on.

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.
Kind of entryWhat it is
FindingSomething you found out
DecisionA decision you made, and why
ShippedSomething you shipped
ReversalSomething you undid, often the best story of all

Set it up

Create an agent key with write access in Borker under Settings, Keys.

Paste one line into Claude Code: Install the Borker build log skill from borker.xyz/skills/build-log

Run /borker-build-log in any session.

The skill asks for your key on its first run. The skill page has the current version. By hand: download the skill and tell your agent to install it from the zip.

What a run looks like

The skill reads your sessions in this project from the last seven days, except the ones you sent before. You can ask for another range, one branch or one ticket. It writes each entry in your own words, picks the channel it belongs on, and asks how you want to review:

  • B, the browser: a page where you tick the entries to keep, edit a title or the text, add or remove the picture, and press Send.
  • T, the terminal: a numbered list, where you keep entries by number.
  • S, skip: nothing is sent, and these sessions are not offered again.

What leaves your machine

The skill removes the keys, emails, wallets and pasted blocks it recognizes before anything is read. The agent writes entries that name no client, person or employer unless you asked. The review page marks every name left in an entry and one click takes it out. Only the entries you keep are sent.

Send refuses an entry that still carries an email address, a key, a wallet address or a block of pasted data. Nothing goes until you take it out.

On the Sources page

Your entries arrive on the Build log tab, in the order they happened, as Not yet planned. Each entry shows its number, its day, its kind, and the background you gave the writer, which is never posted.

The switch on the Sent by your agent card in Settings, Sources decides who plans them:

  • New entries: Borker paces them (the default). Each night Borker plans new entries, oldest first, on the next days the channels picked for each one post.
  • New entries: I plan them. New entries wait for you on the Build log tab. Tick entries and choose the start, the pace and the voice, then press Plan them.

On any one entry, Plan it picks its day and channels, Reschedule moves it, Remove from plan takes it out for good, and Skip it sets it aside.

From entry to post

A planned entry is a place in your week, nothing written yet. 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. It carries the entry's picture, if it has one, and no link. Its card reads "From your build log: Day N", counted from your first entry. The posts land in the Command Center, and they wait for you in Review like every other post, unless their voice publishes on its own.

On this page