Skip to main content

Build in public with Claude Code, without stopping to write

Building in public costs time most builders do not have. Borker's build log lets you build in public with Claude Code anyway: a skill you add to Claude Code reads your coding sessions, you keep the moments worth sharing, and Borker turns them into posts. Other coding agents can send entries to it through Borker's API or MCP server.

  • Your first week, 10 posts, written before you pay
  • You approve every post, or let Borker publish on its own
  • $19 a month with posts included, or $9 on your own AI key

Building in public turns into a second job

You spend the day heads-down with your agent, fixing, deciding and shipping. By evening the post about it never gets written, and your posts stop for weeks.

When you do post, it is a screenshot without the why. The interesting part, the dead end and the call you made, stays inside the session.

What builders say about building in public

  • How do you do it without it becoming a second job?
  • The hard part is posting when nothing is working.
  • I can build anything and reach no one.
  • I hate writing marketing copy.
  • Those who write their own posts will always win.

From public developer forums and indie hacker discussions, shortened and left unnamed. Not one of these people is a Borker user.

Five reasons people stop posting, and what Borker does about each

  1. It sounds like AI

    A post that reads like generic AI writing is marked before you approve it. You can allow the phrases that really are yours.

  2. It doesn't sound like me

    Borker learns how you sound from writing you give it, and every draft follows the rules you set for that voice.

  3. There is no time

    Borker plans the week and writes each post. Your part is reading it and saying yes, no or change this.

  4. Something goes out I didn't mean

    Borker states only facts you wrote down, and nothing is published until you approve it. If you let Borker publish on its own, a post that touches a word, rule or topic you told it to hold still waits for you.

  5. Posting into silence

    Borker promises no reach. What it does is keep you posting at the pace you chose, on the channels you picked, which is the part you control.

From your sessions to your posts

Four steps, two of them on your own machine. Nothing leaves it until you choose the entries.

  • 7days of sessions read by default

    It reads your sessions

    Run the skill in a project. It reads your Claude Code sessions there from the last seven days, skipping any you sent before. You can ask for another range, one branch or one ticket.

  • It takes out what is private

    On your computer, it boils each session down to what you asked your agent, its closing replies, which files were written, the images referenced, the commit messages from that time and the errors you ran into. Then it removes the email addresses, keys and other secrets, wallet addresses and blocks of pasted data it recognizes. Your coding agent reads that cleaned summary, never the raw session.

  • 4kinds of entry

    You keep the moments worth sharing

    Your agent writes each moment as an entry in your own words: something you found out, a decision, something you shipped or something you undid. It suggests the channel each one belongs on. You review them in your browser or in the terminal, edit any of them, and keep the ones you want.

  • Borker writes the posts

    The entries you keep arrive in your build log in Borker, in the order things happened. By default Borker places them on your next posting days, oldest first, and writes each post a few hours before it goes out, in the voice of its channel. The posts wait for your approval like every other post, unless you let that voice publish on its own.

An example week from a build log

Sam is an example, not a customer. He builds a search tool alone with Claude Code and posts on X, with Bluesky alongside. The entries he keeps fill his posting days. A feed of releases from the framework he builds on, and his own changelog, fill the rest.

  1. MondayXPersonalSearch results came back in the wrong order for an hour. The cause was one missing tie-breaker.Build log, Day 21
  2. WednesdayXPersonalI am keeping search inside the database for now. A separate service would cost more than it saves at this size.Build log, Day 22
  3. ThursdayBlueskyPersonalThe new release of the framework I build on changes how pages are cached. What that means for a small app.A framework release feed
  4. FridayXPersonalI moved search back to the database after two weeks on a separate service. Here is what went wrong.Build log, Day 23
  5. SaturdayXPersonalThis week's changelog as a thread: three fixes, one feature, one thing I took back.His changelog feed

Day numbers count from the first entry, in the order things happened. A week where nothing shipped still has the news feeds and the changelog.

One session, from entry to post

The entry the skill wrote from one of Sam's sessions, a background note that is never posted, and the X post Borker wrote from them.

The entry Sam keptReversal: moved search back to the database

What happened, in Sam's own words

Two weeks on a separate search service. Indexing lagged behind every write and the bill doubled. Search is back in the database with a better index.

Background note for the writer, never posted

The slow queries were all on the largest table. Mention the index, not the table.

The X post, Day 23

I moved search back to the database. Two weeks on a separate service: indexing lagged behind every write, and the bill doubled. A better index fixed what I thought needed a new system.

An example. The post carries no link: posts from your build log never do.

The path an entry takes

A commit log says what changed. Your sessions say why: the dead end, the call you made, the thing you took back. The build log reads your sessions and uses the commit messages only as background.

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.

What leaves your machine

Only the entries you keep reach Borker. Each one carries:

  • Its title
  • What happened, in your own words
  • The day it happened
  • Its kind: a finding, a decision, a ship or a reversal
  • A short background note for the writer, never posted
  • At most one picture, if you chose one
  • The channel it is for

Before your agent reads anything, the skill removes email addresses, API keys and other secrets, wallet addresses and blocks of pasted data, where it recognizes them. When you send, it checks each kept entry again: one that still carries any of those is refused, and nothing goes until you take it out.

Your agent leaves clients, people and employers out of an entry unless you asked for them. The review page marks any name left in one, and one click takes it out.

The skill sends Borker nothing else. Your sessions stay where Claude Code keeps them, the review page runs on your own computer, and your agent key is saved in a file only you can read. Sessions you sent or skipped are not offered again.

Set it up in three steps

  1. 1

    In Borker, open Settings, then Keys, and create an agent key with write access.

  2. 2

    Paste this line into Claude Code:

    Install the Borker build log skill from borker.xyz/skills/build-log
  3. 3

    Run /borker-build-log in any session.

The skill needs Bun, the JavaScript runtime, on your computer. It asks for your key on its first run.

What developers doubt

  • Nobody cares about my updates.

    The build log keeps findings, decisions, ships and reversals: the reasoning, not the screenshot. You keep only the entries worth a post.

  • It will leak a client name or a key.

    Private data is stripped on your machine first, and a kept entry that still carries an email, key or wallet is refused. A name left in an entry is marked for you to take out.

  • I don't use Claude Code.

    The skill reads Claude Code sessions only. Any other agent with a write key can send entries through Borker's API or MCP server, and a changelog feed works with no agent at all.

Developers ask

Does the build log read my code?

It does not open your source files. It reads your Claude Code sessions in the project: what you asked your agent, its closing replies, the names of the files written, the images referenced, the commit messages from that time and the errors you ran into. Private data it recognizes is removed before your agent reads any of it.

What is sent to Borker?

Only the entries you keep: each one's title, what happened in your own words, the day, its kind, a background note for the writer that is never posted, at most one picture you chose and the channel it is for. Nothing else.

Will it post without me?

Not unless you set it to. Each post waits for your approval, unless you set its voice to publish on its own. You also choose which entries are sent in the first place.

Does it work with Cursor or other coding agents?

The skill reads Claude Code sessions. Any other agent with a write key can send entries to your build log through Borker's agent API or its MCP server.

Can an entry be sent twice?

No. Sessions you sent from are not read again, and sending the same entry again changes nothing.

What do I post in a week when nothing shipped?

Posts from your topics, reactions to the feeds you follow and your changelog fill those days. The build log adds posts only when you keep entries.

Can the posts go to X and Bluesky in different lengths?

Yes. Each post is written for its channel. On X a long post becomes a thread that fits the length X allows you, which you set on that channel as Free, Premium or Premium+.

Sound like yourself. Start with a real week.

Borker writes your first week when you sign up, before you pay or connect anything.

Create your account