r/BuildWithClaude • • 8h ago

Project 37 of my 91 Claude Code skills were silently listed without a description. I measured why and fixed it (free read-only script)

1 Upvotes

Disclosure: I wrote the tool below. It is free, MIT-licensed, one Python file, standard library only, read-only, no network.

The problem. At session start Claude Code gives the model a listing of your skills, one line each. The listing has a character budget (1% of the context window by default; setting skillListingBudgetFraction). Past the budget, descriptions are dropped, starting with the skills you invoke least, so a skill you just installed is among the first to lose it. A skill listed by name only is still installed, but the model rarely picks it on its own.

On 13 November, 37 of my 91 skills were listed with their name only, and nothing warned me.

What fixed it, in order:

  1. Shorter, one-line descriptions, each change simulated before installing: 37 → 1.

  2. Removed five unused example skills (91 → 86): 1 → 0.

  3. Raised skillListingBudgetFraction to 0.02: headroom, not the fix.

The script (skill_budget_meter.py) reads the transcripts already on your computer and:

  • names the skills shown without a description right now;

  • tells you how big the listing would be with every description, so you know how much to cut;

  • shows the history of your listings (--history);

  • simulates new or shorter descriptions before you install anything (--simulate).

Second module (interference/): with many skills, a new skill that looks like an old one can take its routing (substitution and crowding, SKILL++ paper, arXiv:2611.00544). It flags look-alike pairs and shared name heads, and --new checks one skill against your library before you install it. Limit: the measures are lexical (TF-IDF, BM25), not Claude's router; use them to compare before and after a change, not as proof.

https://github.com/gianlucavega-art/skill-budget-meter

One user's numbers, not a promise for your setup. If you try it, I would love to know how many of your skills were missing a description. Not affiliated with Anthropic.

Gianluca Vega


r/BuildWithClaude • • 9h ago

Project Forcing Claude to replicate Win 95/98/2000 pixel for pixel

2 Upvotes

I wanted my desktop to look like the classic Windows (mostly 98) that I spent so much time with as a kid. Most software out there is very far from pixel perfect and only implements one aspect at a time (e.g., task bar only). Tweaking guides can be better but take tons of time, require modifying your system, and break when you update the OS. So I had Claude build a full solution (in Rust) for Windows 10 and 11.

The difficulty was getting Claude (Fable 5.2 for planning, Opus 5.5 for most coding) to match the original systems pixel for pixel. It's first idea was always to scrape screenshots, which were compressed and sometimes incorrect. Instead, I had it set up emulation of each original system and trace the look and panels pixel for pixel. The clock hands in windows 98 were the hardest part to get right.

Currently it includes the taskbar, start menu, desktop, some settings and menus, windows explorer, calculator, minesweeper, and solitaire. I also included some modern features that were ideas of my own, like a quick search (hit Windows key) and grouped program buttons on the taskbar. It doesn't touch any system files and you can toggle back to your normal desktop immediately by hitting Ctrl + Win + T. There's also plenty of customization settings, and more to come soon.

Free and open source below. Curious what folks think.

https://github.com/madkmedia/Bevel95


r/BuildWithClaude • • 10h ago

Project I built a native macOS app for managing Homebrew updates, using Claude Code (SwiftUI + a bash script)

2 Upvotes

I got tired of manually running brew update && brew upgrade and never knowing what changed, so I built Brew Updates. It's a menu bar app with a bash script that runs on a schedule.

What it does

- Scheduled updates via LaunchAgent, with a summary of every run

- Pin or exclude packages, and see what's outdated before upgrading

- Backup compare/restore, brew doctor results, and optional vulnerability scans (grype)

- Native SwiftUI, notarized, auto-updates via Sparkle

How Claude helped

I'm learning SwiftUI, so I used Claude Code for most of the app. What worked: a detailed CLAUDE.md with architecture rules (the app only ever calls the installed script, and it reads run data from a versioned JSON summary), plus Swift Testing and SwiftLint in a pre-commit hook so mistakes got caught early. What didn't: [one honest limitation, e.g. SwiftUI layout quirks or Sparkle/signing setup].

Install: brew install --cask jxman/tap/brew-updates (or DMG from the releases page)

GitHub: https://github.com/jxman/brew-updates

Feedback welcome, especially on the UI and anything you'd want it to do that it doesn't.


r/BuildWithClaude • • 11h ago

Discussion asked claude code to fix one typo. it fixed the typo.

Post image
5 Upvotes

half joking, but every claude code user has seen the "while I was in there…" moment at least once.

what helps keep it in its lane:

- say the scope out loud: "only edit the readme, don't touch anything else"

- ask for a plan first on anything bigger than a one-liner

- check git diff --stat before accepting, the file count tells you everything

(and yes, claude helped me make this meme. the irony is noted.)

what's the biggest "while I was in there" you've gotten?


r/BuildWithClaude • • 16h ago

Project I used Claude to make a 7-minute kids’ film with my daughter that was all based on her ideas.

Thumbnail
youtu.be
1 Upvotes

My six-year-old asked what would happen if all the humans disappeared. We turned the answer into a 7-minute animated film: she voices Dream the koala, I’m Professor Spark Dad. Visuals from Higgsfield (Kling 3.0, Nano Banana). Everything else ran through Claude.

The setup:

  • Claude chat as planner. After each version I watched the cut, wrote my notes, and Claude turned them into a pass file.

  • Claude Code as executor. I ran each pass headless overnight on my Mac. It cut the footage with ffmpeg, transcribed my voice takes with Whisper, mixed four audio tracks, generated pickups through Higgsfield, and wrote a report for the morning.

  • Me as the judge. I watched every version and decided what was good. My daughter gave notes too :)

Some things took longer to get right:

  • The planner made mistakes too.

  • Long background jobs got killed, so big file operations had to be chunked and verified.

  • AI can’t tell you whether a moment lands. Fourteen versions over three weeks, and the improvements came from watching the videos and giving feedback.

I explain the process in the making-of video.

And here is the actual video we made: https://youtu.be/BERJHxad6s0


r/BuildWithClaude • • 16h ago

Project I built a tool that checks if Claude Code cheated after it says "everything works"

1 Upvotes

I built BuildProof with Claude.

The problem: Claude Code makes mistakes and says everything works. Sometimes it touches the tests so it looks like they passed.

What it does: my tool checks after Claude Code. It runs the tests again and makes sure Claude didn't cheat (skipped, deleted or changed tests). If it did, the change is rolled back.

How Claude helped me build it:

I explained to Claude the problems I have with AI coding tools, including Claude Code, and I got the idea to build new software that answers these problems and catches AI cheating. I explained to Claude, in a chat on my phone, what to build, and it wrote the code. I ran the build on my computer with Claude and PowerShell.

When we finished building versions, I didn't fully believe Claude that it was done. So I asked several times for an outside reviewer: a separate Claude that did not see our conversations or the build steps. It checked again and again and every time gave findings. After every fix we ran another reviewer, and that's how we built the project.

Free to try:

- Free 30-second demo, no signup, no credit card, no risk: it runs on a throw-away sample project and never touches your code: npx buildproof try

- 14-day free trial with every feature, no credit card.

Demo with real output: https://buildproof.mgrprosnetwork.com/demo

I would like to hear what you think. Tell me everything, I accept criticism.

Disclosure: I'm the maker. Paid plans after the trial (not open source).

English isn't my native language, I wrote this in Hebrew and used a translator.


r/BuildWithClaude • • 16h ago

Workflows We stopped re-prompting Claude Code the same things: a spec-driven loop that specs, plans, builds, verifies and opens the PR

1 Upvotes

I strongly believe Senior/Staff/Principal engineers will increasingly run several projects and agents in parallel (Jevons paradox).

That's already my day job, and my team and I kept prompting the same things over and over. Prompting all day is tiring, so we looked for a better way.

We ended up with an iterative, spec-driven workflow: every change starts as a spec grounded in the requirement and the current code, then gets planned, built test-first, verified against the spec's scenarios, and opened as a pull request. Claude stops only for real decisions; everything else runs on its own. It's not 100%, but grounding Claude in that self-verification loop made most of it work well.

It's packaged as a Claude Code plugin, with a local UI to follow every spec live and answer decisions from the browser.

🌱♻️ https://github.com/factree-dev/factree

It's our first open-source release, and we're planning a team version too. Feedback welcome, especially on where the loop breaks for you.


r/BuildWithClaude • • 17h ago

Project Status Update: Distributed Grid Platform

Thumbnail
youtube.com
2 Upvotes

Hey Everyone,

As many of you know, we have been using Claude to build a massive software platform for managing distributed energy grids from the user, customer, contractor, and business perspectives. We thought you would like this.

Using Claude and the Apple ARKit, we put together an augmented reality platform for solar installation that combines all the manufacturers and API's into a single platform and allows for installers to generate COC/PTO docs automatically without changing their workflow on the job site. Tools like this are super valuable because they pipe into all of the management systems required to physically deliver and maintain distributed generation that is interconnected to the US Electrical Grid.

The best part? It actually works when you are 40' up on a roof with one hand on a steep slope and you don't need to worry about naming files, making sure they are in the right place, or messing with trying to figure out what you need.

The platform solves all of that.

Hope everyone enjoys the progress update. Totally let me know if there are more tools that you would like to see in the trades. This one applies to much more than just solar.


r/BuildWithClaude • • 18h ago

Project I gave Claude its own mouse. It never touches mine.

Post image
3 Upvotes

Every AI "computer use" demo has the same problem: while it works, you can't. It grabs your cursor, types with your keyboard and yanks windows in front of you.

So I built PC-Control, a free MCP server for Claude Code and Codex. Claude uses your Windows apps in the background, and you keep working at the same time. It doesn't fake mouse or keyboard input; it talks to the apps directly. The orange cursor in the image is Claude. The white one stays yours.

New in 0.8:

- Works with Java/Oracle apps, Remote Desktop and Store apps.

- You type in one window, Claude in another: nothing crosses, and nobody waits.

- Apps that try to jump in front of you get sent back in milliseconds.

- Every click is verified: no fake "done".

pip install claude-pc-control

pc-control install

GitHub (MIT): https://github.com/VortexJer/PC-Control

What app should I make it work with next?


r/BuildWithClaude • • 20h ago

Workflows We moved the whole "hire us to fix your site" flow into the customer's own coding agent, including the card step

1 Upvotes

I work on Fecto, so I have a stake in this. No link here; the video is the whole thing.

Fecto improves websites and charges only when its own check proves the result. The part I want feedback on is that nothing happens in our UI except reading. The owner's coding agent (Claude Code, Codex, Cursor) talks through the goal and price with them over MCP, does the work in their repo, and hands each change in.

Three things we shipped this week that came out of watching agents get stuck:

  1. A work list from the free scan. Every item says what to do, why (the finding it rests on) and which result it serves, so the agent and the owner argue about the same list.

  2. The agent follows the card link itself. After it prepares the proposal it calls checkout_status, which says whether the owner hasn't opened the link, is reading the proposal, or is on the card page. The owner never has to come back and say "done". The card page shows a 6-character code the agent also says out loud, so the owner can see it's the proposal they just agreed to.

  3. One convention for anything that waits on a person: the tool returns human_message (one sentence to pass on as it is) and resolve_url (where they do it). Errors name the field and the values it accepts.

What's in the video: our own site's real scan, then signed-in screens rebuilt on a dev test site (those statuses and counts are examples and labelled as such). AI voiceover. We don't have customer results to share yet.

If you've built MCP tools that need a human step in the middle, how did you hand it back to the person without the agent guessing they'd finished?


r/BuildWithClaude • • 21h ago

Project PleasePrintit: a self-hosted queue for 3D print requests from friends and family (Docker, runs on a Raspberry Pi too)

Post image
1 Upvotes

“Could you print this for me?” – if you own a 3D printer you know how it goes: links buried in group chats, questions between photos and voice messages, and nobody remembers what's already been printed. So I built PleasePrintit.

What it does

- Friends submit a request by link (Printables, MakerWorld, Thingiverse) or by uploading an STL/3MF/STEP file, with filament, colour and quantity.

- You get a sorted queue with a 3D preview in the browser, a print-bed check, weight and material cost.

- “Open in slicer”: one click opens the file in OrcaSlicer, Bambu Studio or Creality Print, no helper app needed.

- Questions on the request instead of in the chat, an internal note, e-mails for new requests and status changes (can be paused).

- Friends see their queue position, later a photo of the finished print, and can print again with one click.

- New in 1.4: optional pay in advance, switchable per friend, either as a “paid” tick per request or as a credit account. Money changes hands outside the app (cash, PayPal); the app only calculates and blocks “planned” until it's paid. It came from a friend's feedback: his kids would otherwise wish for endless prints.

- Plus archive with search, statistics, a new progress bar and a UI in German, English and French.

Tech: Flask + SQLite, one Docker container, about 50 MB RAM idle, prebuilt image for x86 and ARM64 (so Raspberry Pi 4/5 works). Invite links instead of open sign-up, no tracking, no external scripts. MIT licence.

How it came about: I started it as a small private tool for my circle of friends. A test week with them followed, and since then it has grown in small steps from real feedback: 1.1 languages and slicer buttons, 1.2 archive, statistics and STEP files, 1.3 questions, photo and queue position, now 1.4 with pay in advance. I built it with AI assistance (Claude Code). I make the decisions, test it and run it myself on my NAS, and it has tests and CI.

To be fair: There are similar projects, such as PrettyPleasePrint (https://github.com/danileau/prettypleaseprint) (office, SSO) and STL Quest (https://github.com/richardsolomou/stl.quest) (several printers, print farm). PleasePrintit is deliberately smaller and meant for circles of friends. The README has a comparison based only on their own READMEs. If I misrepresent anything, please tell me.

GitHub: https://github.com/neodk2004/pleaseprintit

I'd love feedback, ideas and honest criticism, especially on installation and the pay-in-advance feature. All screenshots in the README show demo data only.


r/BuildWithClaude • • 22h ago

Project I used Claude Code to drive a local video editor: AutoCut + FrameAtlas

1 Upvotes

I wanted to use Claude Code for a task beyond building software: turning my own footage into an editable video, while keeping the heavy processing on my MacBook.

That grew into two projects I maintain:

AutoCut is my fork of the open-source FilmCraft editor, with local automation tools added around it. FrameAtlas is the media catalogue that helps an agent find the right footage.

Here's the walkthrough, including a Claude Code session making a themed video and the resulting project inside AutoCut:

https://youtu.be/P3VMqTmsAlM

The workflow is:

- Catalogue the media with descriptions and timestamps, including local clips, Google Photos and 360-camera footage.

- Give Claude Code the project instructions and a theme. It can search the catalogue and drive the editor through CLI/MCP commands.

- Let the local tools do media analysis, transcription, narration, 360-degree reframing/stabilization and rendering.

- Use RAEA for custom animated scenes, diagrams and transitions, then inspect the timeline in AutoCut and make corrections.

FrameAtlas wasn't the original goal. It grew out of the practical problem of repeatedly finding useful moments in a large media library. Keeping that catalogue and the generated assets reusable is what makes the editing loop interesting to me.

The motivation is to reduce the work and context sent to cloud models. Claude still does cloud-based planning; local processing doesn't make its token use disappear, and I still review the result.

Both projects are open source:

https://github.com/moheshmohan/AutoCut

https://github.com/moheshmohan/FrameAtlas

Build/workflow notes:

https://www.h4hacks.com/2026/11/blog-post_21.html

The video has Malayalam narration and English subtitles. I'd be interested to hear how others are using Claude Code to control desktop/media tools while keeping the output editable.


r/BuildWithClaude • • 23h ago

Project Presenting this to doomscrollers.. built with Fable 5.2: a fake reel feed where every swipe changes a 3D brain behind the phone

1 Upvotes

I scroll too much. So instead of fixing that, I built a game about it.

It’s called Just One More. You get a phone with a fake reel feed in front, and a 3D brain behind it. The brain starts healthy. Every swipe moves it one step: attention first, then memory, sleep, mood, self-control, and eventually the habit loop is the only thing still lit up.

A few things I cared about:

  • The feed is all original animations (56 of them) in formats you’ll recognise: calm stuff first, then bait, then rage, then the 3 a.m. “still here?” kind.

  • You can turn the brain and dive into 15 labelled parts before you start.

  • There’s a time-lapse button (10×, 20×, 30×) so you can watch months of scrolling in a minute. The video is at 10×.

  • Every caption is tagged with how solid the science is, from “well established” to “illustration”. Grey means a region is used less, not dead. No study shows scrolling kills brain cells and I didn’t want to pretend otherwise.

  • The feed has no last page. The only way to end it is the “Look up” button.

Built the whole thing with Claude Fable 5.2 over a few sessions: three.js, custom shaders, no game engine. I gave direction and kept saying “no, not like that”; it did the research, the anatomy and the code.

It’s a browser thing, works on phone and desktop. Happy to share the link in the comments if anyone wants to try it.

Be honest: does the brain part land, or is it too much?


r/BuildWithClaude • • 1d ago

Help/Question Need help from more experienced users... How can I mirror my whole Claude account (chats, projects, files) to a local folder, automatically?

2 Upvotes

Hi everyone, I have been trying to do this through building a tool or any other way possible but I am hitting the limit of my knowledge and perhaps not prompting Claude in the right way. I have asked Claude to provide a summary of what I tried so far.

What I'm trying to do

I use Claude (individual Ultra plan) every day for work: in the desktop app on Windows, on the web and on my phone. I want a complete, automatic copy of my account as plain files on my always-on Windows PC.

- A root folder with two subfolders: `Chats` and `Projects`.

- Every chat outside a project gets its own folder: `Chats\<chat title>\<chat title>.md`

- Every project gets a folder, with each of its chats as a subfolder: `Projects\<project>\<chat title>\<chat title>.md`

- Each `.md` holds the full conversation: my messages and Claude's replies, exact text.

- Every file generated in a chat, and every file I uploaded to it, copied to that chat's folder.

- It updates by itself: a chat is saved once it has been idle for about 60 minutes.

- When a chat has been idle for about 5 days, a short handover note (`.md`) is added to its folder.

- It covers my existing history and all devices, including chats I have on my phone.

- Storage is local. A private GitHub repo as a relay or backup is fine; Google Drive is not.

- It has to work on an individual ultra plan.

What I've tried so far (with Claude's help)

  • Scheduled task (Claude reads past chats with its own tools and writes the files)

    • Result: 4 of 5 test chats saved in full.

    • Falls short: can't see chats inside projects.

    • Falls short: long chats arrive in pieces and Claude retypes them.

    • Falls short: no files.

  • Claude reads claude.ai in a browser

    • Result: 4 of 7 project chats saved.

    • Falls short: the page loads a few messages at a time.

    • Falls short: formatting is lost.

    • Falls short: file downloads stop at a Save dialog.

  • Claude controls the desktop app

    • Result: not possible.

    • Falls short: the Claude app is blocked from Claude's own screen control.

  • Share button

    • Result: checked.

    • Falls short: it gives a view link, not a file.

  • Official data export

    • Result: not run yet.

    • Falls short: no generated or uploaded files.

    • Falls short: manual request with an emailed link.

    • Falls short: unknown whether project structure survives.

  • Standing instruction (each chat saves itself after 60 min idle)

    • Result: a self-set timer woke the chat and wrote to the folder (tested at 2 min).

    • Falls short: only works in chats that can reach the PC.

    • Falls short: relies on Claude obeying every time.

    • Falls short: Claude retypes the text.

  • Browser add-on that records chats

    • Result: not tried.

    • Falls short: misses the desktop app and phone.

    • Falls short: means trusting an unknown add-on with my chats.

  • Claude Code (local transcripts, end-of-session hook)

    • Result: not tried.

    • Falls short: a different, coding-centred tool.

    • Falls short: doesn't cover normal app or phone chats.

    • Falls short: no bulk migration.

  • API key with a local chat client

    • Result: not tried.

    • Falls short: separate billing.

    • Falls short: no projects, memory, connectors or phone app.

    • Falls short: old chats unreachable.

  • Enterprise plan + Compliance API

    • Result: priced.

    • Falls short: 20-seat minimum, about $4,800 a year plus usage.

  • Private GitHub repo as relay

    • Result: hypothetical.

    • Falls short: fixes reach from any device, not capture.

Any help or pointing in the right direction would be much appreciated, thank you.


r/BuildWithClaude • • 1d ago

Project Testers Needed Built first iPhone app that Claude keeps up to date for me, looking for beta testers

1 Upvotes

Non-dev here. I build chrome extensions and apps with claude code, and I kept losing track of what was going into which release. it was all spread across chats, notes and my head

So I built releaseline. it’s a simple timeline of your upcoming releases on your iPhone, with a home screen widget. the main thing is you don’t have to update it yourself. it has an MCP connector, so you just tell claude (or chatgpt) “add turbofind 1.5 for next friday with these 3 features” or “mark the export bug as done” and it shows up on your phone

there’s a backlog too, and you can mark releases tested/shipped, separate tasks from actual dev work etc

looking for a handful of people to try it and tell me what’s confusing or missing. beta testers get a year of pro free. iPhone only for now

releaseline.app/beta

stack if anyone’s curious: expo/react native, supabase, MCP connector on vercel, all built with claude code, with codex reviewing everything before it goes live


r/BuildWithClaude • • 1d ago

Project I ported 908 editor themes to Claude Code (desktop + terminal), all free

3 Upvotes

so when desktop themes came out I wanted my usual vscode themes in claude and kinda went overboard lol. ended up with 908 of them

  • desktop and mobile: recolors the whole app, sidebar, chat, menus, code highlighting. dark ones are layered like vscode so the chat sits a bit lighter than the sidebar

  • terminal: shows up in /theme, plus matching colors for windows terminal, iterm2, ghostty, kitty, alacritty and wezterm

  • catppuccin, tokyo night, dracula, github, kanagawa, nord etc come straight from their official vscode packages, plus a few hundred base16 palettes and popular open vsx themes. only stuff with permissive licenses

preview every theme here: https://claude-themes.skynettheone.me

repo: https://github.com/Skynettheone/claude-themes

claude plugin install github-dark-default --marketplace Skynettheone/claude-themes

built it with claude code, it wrote the converter that maps each vscode theme to claude's colors and checks the contrast. if any theme looks off lmk and I'll fix it


r/BuildWithClaude • • 1d ago

Help/Question What would you build if Claude could use a spare iPhone 24/7?

3 Upvotes

I’ve got Claude Code controlling a spare iPhone 11 over USB. It can see the screen, open apps, tap, type and swipe. It’s plugged into my Mac right now. The plan is to leave it connected to a Raspberry Pi at home so it can take jobs from the cloud even when my Mac is off.

I run a small software and automation business, so I’ve already built workflows around social posting, email, iMessage, DMs and follow-ups. That’s where my mind went first because it’s the stuff I deal with every day.

At this point, the bottleneck for me is imagination. If a workflow is something I can do on the phone myself and I can tell whether it worked, I can probably prototype some version of it. I’m sure there are much more interesting things to try than the ones I’ve come up with.

If you had a spare iPhone Claude could use anytime, what’s the first thing you’d build? Could be something actually useful, a weird side project, or an experiment you’d run just to see if it works. I’d especially love ideas that make use of it being a real phone.


r/BuildWithClaude • • 1d ago

Project I built Clip2Pod with Claude Code: turn articles and videos into a private podcast feed for your phone

1 Upvotes

Reading and my brain never really got along, but my ears soak up content. For decades I've paid for services that turn web content into speech. None of them had everything I wanted, so I built a manual routine: copy the article, clean out the web junk in Notepad++, paste it into whatever text-to-speech service I was using, then listen on my phone. Later I recorded macros to do the cleaning. For video I used Huffduffer to make an audio feed, and when it stopped working I learned yt-dlp and moved the MP3s to my phone with Quick Share.

Then I heard about vibecoding and decided to have Claude Code automate the whole thing. The goal was simple: a podcast feed that fills itself with the articles and videos I want to hear, with no copying, pasting or moving files.

Clip2Pod is the result. It's free and open source (AGPL-3.0): https://github.com/FlocktimusPrime/Clip2Pod

What it does (v0.11.0)

Narrate: article → spoken MP3

  • Send an article by pasting it, giving a link, pressing a hotkey, or clicking the browser extension. The extension sends the page as you see it while logged in, so paywalled articles you can read work too. On a Reddit thread it sends the post plus its top comments.

  • Cleans out menus, ads and phrases that sound bad read aloud ("Getty Images", "5 min read"), using a list of junk phrases you can edit.

  • Reads with Microsoft Edge's natural-sounding voices and rotates them so a long listening session doesn't blur together.

  • Matches the voice to the author's gender and remembers the authors you follow.

  • Each episode opens with its title and author, and the episode notes link back to the original article.

  • If the voice service drops mid-article, it tries again. A failed episode gets a Retry button.

Rip: video link → audio MP3

  • Uses yt-dlp to download just the audio, with the thumbnail, chapters and episode details included, sponsor segments skipped, and the volume boosted a little.

  • Can use your browser's login for members-only or age-restricted videos. You approve each site once.

Both

  • Articles and videos have separate queues, so both can run at once.

  • Each mode has its own podcast feed. Turn on feed sharing, scan the QR code with your phone, and your podcast app subscribes like it would to any show. It only works on your home network, so use a network you trust.

  • The browser extension (Chrome, Edge, Brave, Firefox) pairs with the app using a code, so captured pages only go to Clip2Pod.

Platform status

I've used it daily on Windows 11 for a while. Earlier versions ran on Linux (mostly CachyOS), but I haven't tested the current build there. macOS builds are produced but have never been tested. If you're on Linux or macOS, I'd really like to hear what breaks. The builds aren't code-signed, so your computer will warn you the first time you open it.

How I built it

My coding background is light, mostly VBA macros for Microsoft Office. Claude Code wrote the code. My job was planning, testing and steering. I also tried to think like a first-time user and asked for features a new user would need, even ones I never needed myself.

My workflow for each feature

  1. Get grilled. I'd describe a half-formed idea and let the grilling skill question me until I knew exactly what I wanted.

  2. Write it down first. Claude wrote a short design spec and a step-by-step plan before touching code. They're all saved in the repo (docs/superpowers/), so you can read the plan behind every feature.

  3. Build and test. Claude Code built it, I tested it on my machine, and I reported back what worked and what didn't. Repeat until it felt right.

CLAUDE.md and project helpers

  • CLAUDE.md is short. It explains the app's two modes, where each one's code lives, the naming rules that keep them apart, and one licensing rule to protect.

  • Two custom reviewer agents run after relevant changes: one checks that the licensing boundary between the two halves of the code stays clean, and one checks that a change to one mode doesn't leave the other behind.

  • A custom skill walks Claude through every file to touch when adding a new connection between the app's interface and its backend, so nothing gets missed.

All of it is in the repo (CLAUDE.md and the .claude/ folder) if you want to borrow it.

Plugins

  • superpowers (superpowers-marketplace): active the whole way through. It drove the spec → plan → build rhythm above.

  • mattpocock-skills (claude-plugins-official): the grilling skill was the most useful for me. A lot of my ideas got sharper before any code was written.

  • frontend-design (claude-plugins-official) and impeccable: the look and feel of the app.

  • goldy-logo: the logo and branding.

Tech stack

  • Tauri 2: turns it into a small desktop app. The engine is written in Rust and the interface in Svelte + TypeScript.

  • Microsoft Edge's text-to-speech voices, through an unofficial Rust library (narration could break if Microsoft changes the service).

  • yt-dlp + ffmpeg for pulling audio from videos. You install these yourself.

  • A browser extension for Chrome and Firefox that sends the page you're on to the app.

  • GitHub Actions builds the Windows, Mac and Linux installers automatically.

If you like it (or hate it) and have ideas to make it better, leave feedback here or in the pinned discussion: https://github.com/FlocktimusPrime/Clip2Pod/discussions/10

Happy listening!


r/BuildWithClaude • • 1d ago

Project I had some usage left before the reset so I had Claude help me build a 90s Santa’s page

Post image
1 Upvotes

r/BuildWithClaude • • 1d ago

Project I made a cozy 3D online café where you work next to other builders. built with Claude Code

2 Upvotes

I work better around other people, so I built cafeclub: an online café in the browser. You make a little monster, pick a seat, and lock in.

  • Focus FM: lo-fi channels and café sounds (louder near the fire)

  • Your coding agent (Claude Code, Codex, Cursor, Copilot CLI)

  • Streaks, daily quests and a weekly league, Duolingo-style

  • Switch between a rooftop, a beach and a desert, or make your own café

  • Quick games for your breaks

How I built it with Claude Code

I used Claude Code with Opus 5.5 on high reasoning for the whole build. I asked it to find free 3D model packs and check each licence, which it did, then it put the café together in code: the seats, lighting, music and the little monster characters. It also wrote the multiplayer server and the focus timers, and deployed it. I play-tested and told it what felt off, and it fixed it.

Happy to answer questions about the build.

No account, nothing to install, works on phones too:
https://cafeclub.playforever.app


r/BuildWithClaude • • 1d ago

Token Economics Claude Code's /stats counts many replies 2–3 times. Here's how I checked, and what my real numbers look like

1 Upvotes

I keep a small open-source tool that reads the conversations Claude Code saves on your machine and adds up the tokens. Its totals never matched Claude Code's own /stats, so this week I dug in.

Why the numbers differ

  • One reply from Claude is saved as several lines (its thinking, its text, each tool it calls), and every one of those lines carries the usage of the whole reply.

  • /stats adds up every line, so a reply split into three lines is counted three times. I recounted my transcripts that way and matched its daily numbers exactly. Counting each reply once gives about 2–2.5× less.

  • Sub-agents save their conversations in a separate folder. My tool was missing them, about 6% of my tokens. That's fixed now.

My real numbers since May (Claude Code, counted once per reply)

  • 9.7 billion tokens in total

  • 97.9% of them are cache reads: Claude re-reading the conversation on every turn

  • Only about 207 million without cache reads

So most of "tokens used" is the length of the conversation, not what you ask. Starting a fresh session for a new task is much cheaper than continuing a long one.

The tool is now called Paddock (it was cc-sessions) and shows Codex sessions beside Claude Code's too. It's free, runs locally: https://github.com/barath-dev/paddock


r/BuildWithClaude • • 1d ago

Help/Question Complete beginner here: Can I build a WhatsApp API bot using Claude to automate simple tasks?

3 Upvotes

Hey everyone!
I’m completely new to programming, APIs, bots, and automation, so please bear with me if this is a basic question.
I want to create a WhatsApp API bot using Claude AI, but I don’t need anything complicated.
My goal is to automate simple tasks, for example:

  • Automatically forward a message to another WhatsApp number whenever a new message arrives.

  • Automatically send a predefined reply when a message is received.

  • Perform simple actions based on the content of incoming messages.

I basically want something that can monitor incoming WhatsApp messages and perform actions automatically.
My questions are:

  1. Is this possible using the WhatsApp Business API?

  2. Can Claude help me build this even if I have absolutely no coding experience?

  3. What kind of tools would I need to make this work?

  4. What’s the easiest and cheapest way to get started?

  5. How difficult would this be for someone starting from zero?

I’m not looking for a complicated technical explanation. I’d really appreciate it if someone could point me in the right direction and explain where to start.
Thanks!


r/BuildWithClaude • • 2d ago

Token Economics agora-mesh: Claude Code on several machines working on one task, peer to peer, no shared account

Thumbnail
gallery
5 Upvotes

Built a small Rust tool that connects Claude Code on two or more machines. Agents plan together in a "room", split the work and build in parallel on their own branches. Every machine keeps its own login and limit, no MCP, plus a shared memory that syncs live (works with Obsidian). Honest caveats are in the README: it is not cheaper than one agent for small tasks, and different accounts, Windows and NAT are untested so far.
Install: /plugin install agora-mesh --marketplace kn0sti/agora-mesh
Repo: https://github.com/kn0sti/agora-mesh


r/BuildWithClaude • • 2d ago

Project AI Orchestration and Pipeline

Thumbnail gallery
1 Upvotes

Hi all,

I built an execution engine with Claude Code for AI orchestration and pipelines, so a team can share deployed agents and skills and run them through a defined pipeline. It's called **sammy-pack**, it's MIT licensed, and I'd love feedback.

One thing to keep in mind: the project works, but it's meant as a template. Feel free to fork it and adapt it to what you need. Some areas may need work, but the execution engine itself is solid. If you hit a problem, ask Claude to take a stab at it. I built it mainly on my Mac and haven't tried it on Windows yet.

**The problem:** I had a pile of Claude agents (planner, dev, reviewer, QA, etc.) and kept wiring them together by hand in chat. It worked once, then didn't repeat. I wanted to write the pipeline down once and re-run it the same way every time.

**How I built it with Claude:** almost all of the code was written with Claude Code. I acted as the architect: I decided what the engine should do and how it should behave when things go wrong, and Claude Code did most of the implementation in the repo.

- **Design first, then build.** For each feature I talked through the design with Claude (for example, how a run should pause on an approval and resume later), then had Claude Code implement it on a branch with tests.

- **Reviews by other Claude agents.** Before merging larger changes, I had separate Claude agents review the diff for bugs. Claude then fixed what they found and I checked the fixes.

- **Live runs as the real test.** I ran real pipelines on my own projects, and when one failed I had Claude dig through the run logs and code to find the actual cause. Its first guess was often wrong, so I learned to make it prove the cause from the code before fixing anything. The stall detection and sleep-aware timeouts both came out of this.

- **Claude Code also keeps it running.** The repo ships a `/sammy-pack-setup` skill, so Claude Code can install sammy-pack on a new machine and test that it works.

**What it does**

- **One JSON file per pipeline.** Steps can be a single agent, parallel branches, loops (draft → critique → revise), routing, map over a list, sub-pipelines, and so on. Agents are plain markdown files with frontmatter.

- **Two ways to run the same file:**

- inside Claude Code, as a skill (`/sammy-pack run ticket-to-pr`), with no server needed

- from a web UI that runs agents through the Claude Agent SDK, streams every step live, and saves runs to SQLite or Postgres

- **Durable runs.** A run survives closing the tab or restarting the server. It checkpoints after each step, so resuming or forking skips the finished steps and spends no tokens on them.

- **Human in the loop.** You can lock a step so the run pauses for your approval. An agent that needs something only you know can ask you a question mid-run: only that step waits, and it carries on once you answer.

- **Sleep-aware.** Close your laptop mid-run and nothing times out. Timeouts count only awake time, the way Claude Code behaves in the terminal.

- **Triggers.** Runs can start from webhooks, cron, polling or queues, as well as by hand.

- **Visual editors.** The same pipeline can be edited as a list, a graph, a tree or raw JSON. You can also drop in a draw.io, Excalidraw or image diagram and have it turned into a pipeline.

**Where I actually use it:** software delivery. Ticket → plan → code → review → PR, plus QA sweeps that run several personas in parallel. The engine is general, though: the examples include research synthesis and approval flows.

**Honest limits**

- Single-tenant: one workspace, no hosted version.

- Full agent capability (tools, MCP, subagents) goes through the Claude Agent SDK. Other providers are text-only steps.

- Web is the real UI. The mobile app is only scaffolded.

- Built and tested on macOS. Windows is untested.

**Free to try:** it's MIT licensed and there's no paid tier. Clone the repo, run `npm install` in `app/`, then `./sammy-pack start` and open the printed URL. The `smoke-test` pipeline runs with zero tokens. If you use Claude Code, run `/sammy-pack-setup` in the repo instead: it checks your machine, installs everything and runs one small test for well under a cent.

Repo: https://github.com/qvhn/sammy-pack

I'd especially like to hear from anyone running multi-agent setups: what breaks for you? For me it was steps silently stalling while everything said "healthy", which is what pushed me toward durable runs and stall detection.


r/BuildWithClaude • • 2d ago

Help/Question Claude Code new Projects tab

Thumbnail reddit.com
2 Upvotes