buildarc
CLI Tool · Open Source · Nothing to Configure

Your build story,
recovered.

One command turns your Claude Code sessions into content you can actually post.

The Gap

You built something worth sharing.
Then you opened a blank editor.

You vibe coded for weeks. Dozens of sessions. Decisions that shaped the whole project. A pivot that saved it.

Then someone asks what you built. Or you decide it’s time to post a thread. You open the editor and…nothing. The story is gone. It’s buried in .claude/projects/ across 45 session files you’ll never reopen.

The gap between building and sharing shouldn’t be this wide.

45 sessions · 87 moments · 0 posts written
What You Get

Content you can actually post.

Same build story. Three formats. Ready in seconds.

@yourhandle
Thread
1/ Built a SaaS with Claude Code over 6 weeks. 45 sessions. Here’s how it went — the decisions, the pivots, and the moment that almost killed it.
2/ Week 1–2: Setup and architecture → [DECISION] Cookie-based sessions, not JWT → [DECISION] Postgres over MongoDB → Felt fast. Everything worked on the first try.
3/ Week 3: The pivot → Twitter API costs $200/mo for signal collection → [PIVOT] Switched to free sources (HN, Reddit, GitHub) → Got 250 signals per run for $0
4/ Week 6: Ship it → [EMOTION] "The story was disappearing between sessions" → That realization became buildarc → One command to recover the build story

One command. 45 sessions → a thread you can post.

Extraction finds the moments. Your Claude CLI turns them into a story.

Origin Story

I spent six weeks building ScoutAgent with Claude Code. Forty-five sessions. When I tried to write a build-in-public thread, I realized the story had vanished — buried in thousands of lines of tool calls and progress events inside .claude/projects/.

So I built buildarc. One command to turn those sessions into something I could actually post. The ScoutAgent thread was its first output.

Session #12 — Auth debugging
Session #23 — API pivot
Session #38 — Deploy fix
Output

4-tweet thread covering 6 weeks, 87 key moments, and the pivot that saved the project.

Your build story is already written.

It's in your session files. One command to get it out.

Runs Locally
Run once to extract. Run again with --tweet to generate.
View on GitHubFree and open source. MIT licensed.