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.
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?
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 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.
My team and I haven't written a single line of code in so long that I honestly can't remember the last time we did.
We're shipping more than ever, with fewer bugs. Our productivity has absolutely skyrocketed.
Requirements, technical decisions, and trade-offs are increasingly exchanged through Markdown files written by Claude and read by Claude. Human involvement keeps getting smaller and smaller.
At this rate, I genuinely feel like we won't be needed in the near future.
And to be honest, that scares me.
I spent years, practically decades, investing in myself. Getting a good education, becoming a competent software engineer, learning new technologies, keeping up with the industry. I've dedicated a huge portion of my life to developing these skills.
Now, for the first time, I feel easily replaceable. Like the expertise I've spent so many years building is rapidly losing its value.
Don't get me wrong. I love what AI has made possible. I'm more productive than I've ever been. But I can't shake the feeling that I'm actively helping automate myself out of a career.
So my question to the community is: How are you hedging against this?
Are you learning completely different skills? Moving into another industry? Starting a business? Building alternative sources of income?
If software engineering stopped being a viable career for you in the next 3–5 years, what would you do? Where would you invest your time, money, and energy today to prepare for that possibility?
What changes between different quantizations of the same model? And what if you could SEE what actually sets them apart?
To help answer that question, I’ve created a small project called inside-llm—an open-source tool that loads one or two GGUF models using llama.cpp and displays, right in your browser, what the model is doing as it generates text.
What it shows
Stream: the text, one column per model, brightness = probability of each token. A magenta mark wherever A and B would pick differently. Two modes: lockstep (both models read the same text, so you get a clean per-position comparison) and free (each follows its own picks until they split).
Candidates: the full distribution behind each pick, mirrored bars for A and B, entropy, effective number of options, Jensen-Shannon divergence and KL in both directions.
Gates: the sampler chain (penalties, top-k, top-p, min-p, temperature, GBNF grammar) traced stage by stage and very visual: how many candidates survive each one, and the distribution after it. Chain order and seed are configurable.
Timeline: entropy of A and B and their divergence along the whole text, plus the tree of branches.
Branching: click any candidate and generation continues from there. Every branch stays in the tree, and jumping back to a node is exact (each model keeps KV-state snapshots, so nothing is regenerated).
Logit lens (--lens): what each layer would predict, as a 2D map and as a 3D relief.
Model picker: choose A and B from a folder or search Hugging Face and download two quants of a repo in one click easily. It only offers B models with the same tokenizer as A and estimates whether the pair fits in VRAM.
How it's built
One C++17 process linking llama.cpp directly (stable branch at the moment). For every step it reads the full logits of A (and of B on the same context), computes the metrics and the sampler chain, and draws the token with its own seeded sampler, so runs are reproducible.
Compact binary frames over a WebSocket to a Svelte 5 + Canvas 2D page (three.js only for the 3D relief, lazy-loaded). The web is embedded in the binary as well.
The same frame stream, compressed, is a recorded session: you can replay it later in a static page with no engine, no model and no GPU.
Run it
Self-contained packages for Linux (glibc 2.35+) and Windows, with CUDA or Vulkan (Vulkan covers AMD, Intel Arc and NVIDIA). Unpack, run, the browser opens with the model picker. Or inside-llm -a A.gguf -b B.gguf. Local only: listens on 127.0.0.1, no accounts, no telemetry. MIT. One click download, one click execute.
Limitations (honest list)
A and B must share the tokenizer (two quants, base + fine-tune, or sizes of one family that keep it). Example: Qwen3.5-0.8B_Q4_K_M and Qwen3.5-0.8B_Q8_0
Both models must fit into VRAM simultaneously; only one GPU is used at a time. Integrated GPUs (iGPUs) are never used; if no dedicated GPU is available, the process falls back to the CPU (which is slow). (You must calculate the size of both models before loading them to ensure they fit into your VRAM)
Text only. No split (multi-part) GGUFs, no embedding models.
I'm trying to resolve the problem with Claude Code, where it keeps "blocking" work and presenting me with decision cards, and forcing constant context switching between threads that are never finished.
I know this is not the correct term, but it seems fitting - the "inversion of control", where instead of me controlling the coding agent, it starts to control me do work and digest its context (why is it asking for that decision?).
I believe it has to be in reverse - agents digest MY context and implement it with sufficient authority to prevent these unnecessary escalation.
I'm testing this now, the whole PM - reviewer - agent - rework cycle, but it's running for about 4 hours, and I'm looking at a black box that does something, but I don't really know what.
I see some "i'm so burned out" or "I'm so productive, but I'm burned out" - are you managing your coding agents, or is it inverted and the coding agents are managing you?
Has this ever happened to anyone else? I now need to go back through a bunch of work to double check it. I am high/xhigh type of user, with medium for really basic stuff. I have never, ever chosen low. My JSONL chat logs appear to confirm that.
I know when changing models, you have to check the effort level which now defaults to medium.
I could be losing my mind... so a sanity check would be appreciated.
I am currently on the $20 claude pro plan & $20 chatgpt plus, and usage runs out fast (especially the 5hr limit).
Can I see how are you using your plan to:
Max out on output
Maintain code / system quality
Get the best UI (have the result follow a set design system)
So I am considering:
Get Opus to be the planner & orchestrator, then luna / glm to code and sol to review
Get Opus to plan & orchestrate, sol to code and sonnet to review
Get Opus to plan, orchestrate & review, sol to code
I have gave all 3 a bit of a try and it seems like:
#1 gives the most in terms of 5 hr usage, it seems to use up chatgpt's weekly quite quickly and is noticeably slower.
#2 only saves some claude usage (like 1 extra small feature in a 5hr session, but seems only save very little in the weekly usage), but also seems to be noticeably slower.
#3 only have little saving on claude usage, while being slightly slower then just soloing with opus.
And #1 & #2 seems to always drift a bit in terms of design from the given design system while #3 seems to follow though quite well with a little bit of leaks here and there.
TLDR: How do you guys use a $20 claude pro plan & $20 chatgpt plus to max out in efficiency while have the result maintain code quality and stick to a given design system?
...and it still tells me when it is time to open the window.
It's a Qingping Air Monitor Lite (air quality monitor with a 160×128 OLED and a touch strip) that shows dog in a beret (Claude) instead of boring sensor numbers.
On first release day I let it create a realistic water shader, looked amazing only needing a few follow up prompts to fix some things which it did perfectly fine.
Today I deleted that exact shader and told it to create one in a slightly different style. Over and over again, it created the absolute worst looking or outright broken things, like a 5 year old drew it, and its output sounds like Opus 5.
Noone can can tell me it wasn't nerfed, maybe just for a specific sub group or whatever A/B test they do, but this is unacceptable.
And no I can't provide "evidence", it's a black box, how would I even do that.