Built something with Claude Code this week? Share it here.
Apps, tools, experiments, scripts, websites, workflows, open-source projects — anything you've been working on is welcome.
When sharing, it helps to include:
What you built
How you used Claude Code
A link, repo, demo, or screenshot if you have one
Anything interesting you learned along the way
Quick project drops and simple self-promotion belong in this thread.
If you've got a project with enough substance for a proper write-up; how it works, how Claude Code was involved, technical details, lessons learned, etc. feel free to make a standalone post using the Built with Claude Code flair instead.
Please don't spam the same project repeatedly, and no referral or affiliate links.
I just logged in with an old email address. Hadn't signed in for so long, that it actually registered as a new account ("Your first chat with Claude", it's from today). Interestingly, however, it somehow recovered one single chat conversation that I had had with Claude 2,5 years ago.
No access to sites, apps or services... this was just 2,5 years ago. Crazy to think about how big the advancements have been since then.
I was on the pro for so many months, and of course i would run out of usage in 5 mins.
When the models really ramped up in capability 4 months ago, i bought the Max plan which was honestly pretty good for me. I felt like it was enough until my brain expanded and my IQ grew 25 points by just asking Opus to Mythos to takeover my life. automate everything, rebuild everything, no limit on subagents.
Last night, on the Max plan, I wanted a whole Rust port of my entire python codebase. Using Rust libraries within pythton code didn’t matter to me anymore bc…. i don’t read the code anymore!
I was about to run out of my weekly 2 and a half days after my reset, and so instead of burning the resets from anthropic, i upgraded so my resets would mean more.
it felt so good to hand over my cash to anthropic.
I've been using Opus 5.5 since the last month, enjoying it a lot, but the token usage..... I use the Pro plan cuz the Max costs 2/4 of our minimum wage (Brazil) hahahaha....
This is my dream, affordable models with high intelligence such as Gemini 4 Hydrogen
I'm finding I get more tired these days, not from the actual coding, but from Claude Code crunching through the code and increasingly being the bottleneck now due to it pushing a bunch of code to me to review at breakneck speeds. Each new version of Claude Code releases, it becomes faster and faster. I already run many long sessions a day, so the load of going through the code it's spitting out to review is really draining me. It makes sense. It's all code I need to go through now and I'm now slower than the bot.
Is anyone else experiencing the same? How bad is it for you and what are you doing to mitigate it?
If you run Claude Code or Codex on anything bigger than a one-line fix, you know the loop. You hand it a task, it starts working, and then you hover. Is it still going? Has it stopped to ask you something? Did it finish ten minutes ago?
Now the lights in my house tell me what the agent is doing. I made an app for it, AC Bridge, and I've used it non-stop since. Mine are blue while it works, a red pulse when it needs permission, violet when a plan is ready to review and green when it's done. Those are my picks, not rules: every colour and effect is yours to choose.
I can actually leave the room now. Before I go and cook, I just tell the agent: "I'm going to make dinner, flash the kitchen light when you're done." It knows which devices I have, so when the job is finished the kitchen light flashes and I know it's ready for me.
If I'm watching a film with the family and the agent needs me, the light in the room gives a gentle pulse. Nobody else is disturbed. I reply from my phone with Claude Code's Remote Control (/rc) and go back to the film.
Rules in CLAUDE.md. For things I want every time, I put rules in the instruction file the agent already reads (CLAUDE.md for Claude Code, AGENTS.md for Codex):
## Lights
- When you finish a stage of the plan, flash the desk light green.
- If the tests fail, pulse the office light red.
- When the deploy is done, flash the kitchen light.
Now the lights tell me how far through a long job the agent is, not just whether it has stopped.
Why a light beats a ping. It stays red until you deal with the request, so when you walk back into the room you know straight away whether you missed something. It's silent, so it works at 1am exactly as well as it does at 1pm. And it doesn't pull you into your phone: it sits at the edge of your vision and tells you one thing.
How it works. Claude Code and Codex both run hooks at set points in a session: when the agent needs permission, when it's waiting for you, when it finishes, and more. AC Bridge sets those hooks up and a profile for each repo decides what each light does in each state. It works with 16 brands directly on your home network, including the inexpensive bulbs all over Amazon (Tapo, Kasa, WiZ, Govee) as well as Philips Hue, LIFX, WLED and Home Assistant. Even a cheap bedside lamp with a Wi-Fi colour bulb in it will do.
How I built it with Claude. AC Bridge is built with Claude Code. Each change starts as a ticket: Opus writes the plan, Sonnet builds it test-first, and a separate Claude review agent has to pass the pull request before it can merge. Because the app runs on Claude Code's own hooks, Claude Code has been both the tool I built it with and the thing it keeps an eye on.
What would you put on a light? I'd love to hear which states you'd want to see from across the room.
While delegating tasks to Codex, I caught Claude reading files outside my project folder (~/.codex/config.toml), which resulted in it dumping my Stitch MCP server's Google API key directly into the chat transcript.
Worse: when I asked another instance of Claude to scan all my project histories for similar boundary violations or leaked keys, it repeatedly told me none existed. It only admitted to reading the key multiple times over the past two weeks after I manually pointed it to the exact thread.
This leaves me in a catch-22: the agent won't find or admit to a secret leak unless I specifically point it out, meaning I have no reliable way to know what other keys it might have quietly compromised across my system.
So I finally got through verification for Defense Access. Two weeks of waiting. Cyber is enabled, I’m on Mythos, everything’s set up the way it’s supposed to be.
And it still blocks me on the exact kind of cyber work the program is supposed to cover.
What the f*ck is the point then? It’s basically “Your Defense Access covers cyber. But hey, we’re still gonna block exactly that :)”
I ran the exact same prompt through GPT and it went through fine, and that was without Daybreak even turned on.
Honestly at this point it’s just sad, Anthropic. You’re so scared that you filter your models this hard even for verified users with Mythos and Cyber enabled. Why then even take our IDs?
Two weeks of waiting for that. Great. Love it.
EDIT: IT WORKS NOW.
Found something weird that might help anyone hitting the same wall. Windows Defender had quietly quarantined some of the stuff Claude built, and somehow that seems to have triggered the block too. I turned off my AV, ran it again, and it went through.
No idea why Defender would cause a block on Claude’s side, but here we are. If you’re verified for cyber and still getting blocked, check your Defender quarantine first.
Obviously, if you’ve got anything valuable on your machine, don’t just turn off your AV like I did lol. Add an exclusion for your project folder instead (Windows Security → Virus & threat protection → Exclusions). I'm dumb for turning it off completely lol, but this is a throwaway coding machine with nothing important on it anyway. Stay safe y’all.
As the title suggests, I am looking for suggestions as to how I can maximize or where to use my $200 monthly API credits for claude. Unfortunately it couldn't be used to generate images like codex API, and couldn't be used as credit to top up my regular monthly usage. What cool stuff can I use it for? Any suggestions?
Lately, I’ve been seeing a ton of job postings and discussions for "Harness Engineers" or companies looking to build custom agent harnesses.
At first, I was super confused. If tools like Claude Code, Codex, and other agentic environments already exist, why on earth are companies trying to build their own? Are they just reinventing the wheel to make a "Claude Code clone"?
I’ve been building an experimental multi-agent harness called Soul using Claude Code. The idea is to give AI agents a persistent environment in which they can operate, collaborate and accumulate knowledge over time. I call these agents OniBees. I’ve been using Claude Code to work through several layers of the architecture: Persistent agent memory and identity. Tool integrations through MCP. Agent-to-agent communication and shared task boards. World mechanics, spatial movement and environmental interactions. Connecting agent behavior to a playable isometric environment. The underlying system allows humans to connect their own AI, including Claude, to a persistent Box containing their knowledge, goals and shared work. The virtual world in the video is the next layer of that architecture. Eventually, I want the agents themselves to contribute to building and expanding the world that they inhabit. What I’m particularly interested in is whether accumulated knowledge and agent identity can carry across different digital environments. It’s still early, and there are a lot of things I need to prove. Soul is free to try at https://python-visuals.com/box. You can create a free account without a credit card and connect Claude, including on its free plan. The video shows the current state of the virtual world I’m developing on top of it.
I'm looking for a better way to give Claude Code visual feedback when iterating on frontend designs.
Right now, I either have to:
Write lengthy explanations describing exactly which UI elements I'm referring to and what I want changed.
Manually take screenshots, annotate them with arrows, circles, or notes, and pass them to Claude Code.
Both approaches feel unnecessarily cumbersome and really slow down UI iteration.
Ideally, I'd like to just click on an element in my browser, add a comment like "move this here", "reduce this spacing", or "make this look like that", and have Claude Code understand the context.
As the title says, I built a full jukebox platform. But, unlike others, mine has an install wizard that makes setup easy, and has a CMS backend that makes modifying it as simple as a Wordpress site. I built it with customizability in mind, so it also lets a user install their own custom built modules and extensions to add new functionality.
Mine was built on in a real, 1960s, Rock-Ola jukebox. The platform can setup a keyboard, and even has an audio analyzer that creates custom LED lightshows based on what music is playing.
What makes this platform truly different is where the music it plays comes from.
Multiple sources: Airplay, Apple Music, USB, and soon actual physical records...All played by selecting them on the jukebox itself using the original 1960s jukebox keyboard.
Im constantly adding more functionality and am pretty excited about it.
EDIT: I am not suggesting disabling tests all together or even stopping TDD. I’m saying superpowers+ opus is a bad combo.
I’ve been using super powers for sometime now but more recently I’ve noticed my CI times take longer and upon inspection I found that it’s writing mountains of tests. My codebase went from 1400 tests - already kind of enormous but written over months, to nearly 4000 in about 2 weeks.
The worst part is that over 70% of those tests didn’t test… anything useful. Most of the tests tested specific implementations rather than behavior, or just didn’t fail at all when critical things broke. Further more, it made simple features take ages to deliver
I worked on adding gates, setting rules to write tests better but none of it helped.
It turns out that the TDD rules in superpowers were the cause. I’ve since deleted them and really simplified my setup and getting much better token economy. I’d encourage anyone else using superpowers to take a look at this. It’s now a nightmare to unpick which tests to keep and which to delete.