
buildarc is a CLI tool that reads Claude Code session transcripts and turns them into content you can actually post. It belongs to the developer tools category, specifically for those using Claude Code for AI-assisted coding. The tool is designed for developers who build with Claude Code and want to share their development journey without manual effort. Its core value is bridging the gap between building and sharing by automatically extracting key moments from session files and generating ready-to-post content in seconds, a process the site demonstrates with outputs like a 4-tweet thread covering six weeks and 87 key moments.
The problem buildarc solves is the loss of narrative during extended AI-assisted coding projects. Developers often spend weeks in Claude Code across dozens of sessions, making critical decisions, pivoting, and solving complex problems. Yet when they want to share what they built or write a build-in-public thread, the story is buried in .claude/projects/ directories. The website illustrates this with '45 sessions · 87 moments · 0 posts written.' The gap between building and sharing is wide because the context is scattered across session logs containing thousands of tool calls and progress events. This matters because building in public requires timely, coherent storytelling that matches the development effort, and manual reconstruction from logs is impractical.
buildarc's extraction feature reads Claude Code session transcripts from the local .claude/projects/ directory. It scans thousands of tool calls and progress events to identify key moments such as decisions, pivots, and emotional milestones. The tool automatically surfaces these moments, like 'Session #12 — Auth debugging' or 'Session #23 — API pivot.' This extraction process works with a single command, eliminating the need to manually parse session logs. The benefit is that developers can recover the narrative of their project without reading through every session file individually, instantly surfacing the most important events that shaped the build.
After extraction, buildarc can generate ready-to-post content using the --tweet flag. The generation phase transforms the extracted moments into a structured thread format, complete with tweet numbering and contextual headings like [DECISION] and [PIVOT]. The example output shows a 4-tweet thread covering six weeks, 87 key moments, and a pivot that saved the project. This feature enables developers to produce polished social media content directly from their session history. The tool also supports three output formats, though the website primarily demonstrates the thread format, giving users flexibility in how they share their stories.
admin
buildarc runs entirely locally, ensuring that session transcripts never leave the user's machine. It is open source and requires no configuration, meaning developers can start using it immediately after installation via npm or GitHub. The tool is lightweight and CLI-based, fitting naturally into existing development workflows. The website emphasizes 'Nothing to Configure,' highlighting its zero-setup approach. Additionally, the tool is self-contained and does not depend on external services, which enhances privacy and reliability. The command-line interface provides two primary operations: extract and generate, with the --tweet flag for the latter.
The overall workflow of buildarc is simple and two-phased. First, the user runs the base command to extract key moments from their Claude Code session files in the .claude/projects/ directory. This step compiles a list of important events and decisions using internal detection logic. Second, the user runs the command with the --tweet flag to generate a thread ready to post. The tool automatically structures the content into a narrative flow, using the extracted moments to tell the story from start to finish. This approach lets developers focus on building while the tool handles content creation retrospectively, reclaiming the story that otherwise remains locked in session logs.
A concrete use case from the website is the creator's own project ScoutAgent. After 45 sessions over six weeks, the developer used buildarc to generate a thread covering the entire build journey, including the pivot from Twitter API to free sources, saving $200/month in costs. The outcome was a coherent narrative that could be posted instantly, something that would have taken hours to write manually. Another scenario is when someone asks a developer what they built; instead of fumbling for details, they can run buildarc and get a ready-to-share summary. The tool also benefits developers who want to maintain a public build log without daily writing, automatically capturing the narrative arc.
buildarc targets developers using Claude Code for AI-assisted development, especially those building in public or maintaining project documentation. It appeals to indie hackers, solo founders, technical content creators, and developer advocates who want to share their work without manual overhead. The tool is available as a CLI via npm and GitHub, and it is open source. There is no pricing or plan mentioned; it is free to use. The primary takeaway is that buildarc reclaims the build story from session logs, making it easy to share the narrative behind any Claude Code project with a single command, bridging the gap between building and sharing.
buildarc is designed for developers who use Claude Code for AI-assisted development and want to share their build stories without manual effort. It specifically targets indie hackers, solo founders, and solo developers who build projects over multiple sessions and need to communicate their journey on social media or blogs. Technical content creators and developer advocates who produce build-in-public content will also benefit from automated narrative extraction. The tool appeals to users comfortable with CLI tools and open source software, particularly those who value privacy and local execution. It is ideal for anyone who has experienced the gap between building something meaningful and having the story disappear into session logs.
Updated 2026-03-02