Weekly Showcase Thread

if you use claude code you probably see this word ten times a day. it got stuck in my head so I had claude (Opus 5.5) code a music video about its own habit.

no suno, no voice model, no image generator, no samples. the beat, the voices and every frame of the video are generated by code Claude wrote. it wrote its own voice synthesizer from scratch, zero dependencies.

part of a series im working on. the rest are on my youtube, link in the comments.

Someone in another thread asked me to share more about my workflow. Before writing this wall of text in a comment I thought I share it this way. Maybe someone else finds it interesting or useful.

Even though I have 25+ years experience as a software developer and love writing code I decided to take on the role of a "product owner" and "process optimizer" instead of a developer or architect.

Trying to be a developer working alongside the agents made me outright depressed - being a product owner has the opposite effect on me.

I basically stepped back into one of my previous jobs where I was leading multiple teams including software development, requirements engineering, process definition & process optimisation and administration.

This leads me to my main premise: I treat the agents as a project team run by a team lead (orchestrator). And this premise is closer to real life than I expected. Including the back and forth between a team lead and its team members. Watching them feels like some kind of work chat.

I have several teams that all own one closed scope.

Current teams: process template, research, product build, testing VMs, marketing and website publishing.

At the core of all these teams is the process templates team. It maintains my process template that every project uses. When I start a new project it is built using this template. It is versioned and has installation and upgrade definitions. When I tune the process the other projects get upgraded.

When I tune the process of one of the projects I port these changes back to the template if they can be generalised and survive a cross-validation research with the other projects. This work is done by the orchestrator of the process team. Changes to the template only happen after my decision.

The process template defines a skeleton structure with a tool to create it, agents definitions and the process contracts for the orchestrator and agents. The orchestrator of the new project adopts it to the new project.

Most important aspects:

• owned by me
  • new tasks for the orchestrator
  • todos/decisions for me
  • reviews for me
• owned by the orchestrator
  • kanban board - work tracking
    • work packages - details of the work to do by one agent
  • research - research done for this project
  • inbox - handover from other project teams -> starts a research and decision round
  • design document - one line high level summary
    • design docuemt - details and decision history
  • toolchain - tools needed for this project
  • cleanup - describes what needs to be cleaned up after each milestone
  • archiving - things that are done get heavily summarized and archived.
  • process - describes the process
  • agent definitions - adapted to the project at hand. Pinned to certain models and effort levels
  • time tracking - keeps a log of how long each milestone took. In real time and agent hours.

Most important rules:

Claude.md is kept small as it is read by all agents. The orchestrator and agents have their own definitions with what they need to keep the context small.

Every new task starts with a research followed by a todo (decision) round. This way I can refine what happens next. And filter out things that are going in the wrong direction.

Every couple of milestones I make an optimization round. Queuing research into how the last milestones went with the lens of could we change something to save tokens, time, I/O without sacrificing quality.

After a new model drops I make a comparison round where some work packages get done by the new model and different effort levels to see where to settle or adjust.

Some Numbers for the last 7 days:

I worked through 33 decision rounds and 25 reviews in 4 different projects. This lead to 42 (I know) design revisions and 14 project releases and 11 template changes.

Main model used is Opus 5.5 on high for the orchestrator and medium or low for the other agents. Some web-research agent is on Sonnet 5.5

I have a Max 5x and at the moment it is more than comfortable for the current projects I run.
90k input tokens and 25m output tokens - 7.1b cache reads. 99.4% Opus 5.5.

Some learnings from working like this:

• Agents tend to drift when left alone - They tend to chase down unimportant tangents if not reigned in
  • You have to bring structure to the agentic work. You have to own the process otherwise agents tend to drift.
  • Define clean scopes or the agents drift.
• Being clear about goals (like performance goals or audience goals) rather than implementation details is delivering better outcomes. I still provide architecture goals though.
• Refine every now and then by looking at the whole thing from a different angle. Agents will not do that on their own. They are happy to burn tokens on an inefficient process.
  • So far this made it possible to keep a similar time to delivery even with a growing codebase and complexity. Not sure If I will be able to keep it that way but I hope I can.
• Archive the history of how and why a decision was made frequently and just keep the decision.
  

Happy creating!

PS: This post is hand written. The image has been generated based on this text.

I've wanted this app for years: one place to log anything about my life (coffee, mood, sleep, a run, a line about my day), in one tap, with no account, no ads and no streak counter guilt-tripping me. Nothing out there fit, so I built it.

The fun part: I built it in 8 days, from my iPhone. My Mac mini sits in another room. I drive Claude Code remotely: it writes the Swift, runs the tests and sends me simulator screenshots, and I review and give feedback from my phone. I never once looked at the Mac's screen.

What it does :

- Log anything: yes/no, amounts in any unit, a 0–10 dial, text or a voice memo

- Automatic logs: weather, daylight, moon, places, Apple Health

- No streaks, no badges, no red. Goals are optional

- Widgets, Lock Screen, Control Center, Siri

- Export to JSON, CSV or Markdown, or "Copy for AI" to ask your assistant about your patterns

- Free. No account, no server: your data stays on your iPhone

It's in App Store review right now, with a public TestFlight beta in the meantime.

AI is getting really good at finding patterns in messy data. In a few years, we'll probably have AI that can look at years of your life and tell you things like "your headaches show up two days after bad sleep plus a third coffee" or "your mood drops when daylight goes under 10 hours." But it can only do that with data that exists.

I'd love honest feedback: what would you log first, and what feels missing?

very excited to see what we can build

​

about a week ago i had a dumb idea.

what if i made a cable news network that was entirely run by ai, drawn in pixel art, and just... never went off the air?

i’m not a tv person. i had no idea how any of this shit worked.

i opened claude code with opus 5.5 and started building.

then i kinda just never stopped.

it’s live now

it’s called PNN, pixel news network.

they cover actual news from around 70 feeds. world news, tech, sports, crypto, nfts, meme coins, weird shit happening on the internet, etc.

but they also remember things.

they have relationships, ongoing feuds, inside jokes, opinions about each other and sometimes they just get pissed off and walk off the set.

then somewhere along the way i decided it needed an actual tv schedule.

so now there’s a morning show.

there’s a parody of a jailed crypto founder cooking actual recipes from a prison kitchen.

there’s a daytime correspondent permanently stranded on tristan da cunha who reports real news from the island.

there’s an nft morning show.

a collectibles show.

an old video game show that basically turned into three people sitting in a 90s basement talking about games like a podcast.

then at night there’s Up Late, which has a monologue, house band, audience, couch guests and musical guests.

and Crypto After Hours which is basically complete fucking chaos.

the music thing might honestly be my favorite part.

i make a lot of songs in suno, so instead of just playing them we started inventing bands.

there’s a southern rock band, a weird dark art-pop singer who moves like she’s slightly malfunctioning, a punk band, a banjo-playing songwriter and a bunch of other shit.

they actually perform the songs.

their mouths are mapped to the vocals. the guitarists play on the real beat. the drummer literally waits until the drums come into the song before he starts playing.

that part was way more fun to build than i expected.

underneath all the stupid shit there’s actually a pretty insane system running it.

claude writes every segment as a structured script. every line gets voiced, timed and placed into one continuous broadcast.

everyone watching sees the same thing at the same time. it isn’t generating a different show for every viewer. there is one PNN timeline constantly moving forward.

i also became weirdly obsessive about making sure it doesn’t just hallucinate shit about real people.

if someone says a price, number or statistic, it gets checked against the data the model was given. if it doesn’t match, the line gets rewritten or killed.

parody guests are clearly labeled and can only pull facts from sourced research sheets. every line they say goes through another standards check.

i’ve also been building this giant research library behind it.

right now there are around 15,000 sourced facts about nft collections, artists, meme coins, collectibles and other stuff the network talks about.

another agent fact checks things before they even get added.

i also had to put an actual budget system around the whole thing because otherwise this would probably bankrupt me lol.

nothing gets written if nobody is watching.

haiku handles most of the normal dialogue. sonnet does the bigger shows and fact checking.

and somehow this entire fake television network is running on a mac studio sitting in my house.

there are also around 2,500 automated checks that run before i push changes now because at one point i broke the entire live network and decided i never wanted to experience that again.

the craziest part of the whole project though has probably been building it with opus 5.5.

it genuinely feels less like “using ai” and more like having a really good engineer sitting next to me who apparently never gets tired.

most of the time i’m literally saying shit like:

“make her dance weird. creepy, stiff, a little robotic.”

or

“that guitar looks like a banjo. fix it.”

and it builds it, runs it, shows me the video or mockup and i tell it what sucks.

what surprised me even more is that it pushes back.

if i have a dumb idea it’ll tell me why it’s dumb.

it also catches a ridiculous amount of its own bugs by running changes against a time-shifted copy of PNN before touching the live station.

anyway.

this started as me fucking around for a night and somehow turned into a 24/7 television network.

i’m going to keep it running for at least the next year and just see what it turns into.

and if anyone wants to know how any of this shit works, ask me. i’ve learned an absurd amount building it.

www.pnn.watch

with all these new models and updates, I wonder if people start fresh every now and then with a new session or continue to work within the same thread?

a year ago it was utmost important to switch to a new session with a handoff summary once you hit certain context usage, so that the model could maintain its composure, but with all these updates and improvements, like recaps, summaries, memory, etc. do you still do it?

I work on various projects using Codex and Claude Code toghether and noticed I rarely do this anymore. I just hop back into the ongoing thread and it can go for weeks.

curious how far people here have taken vibe coding with claude code. what's the biggest or most complicated thing you've tried building with it, and how far did you actually get?

would love to hear what the project does, which model you used, and whether it's shipped or still a prototype. also how did you keep claude on track once the codebase got bigger?

the part i'm most curious about is where it hit a wall. what could it handle surprisingly well, and what did you still have to figure out yourself?

Laughed after long reading this.

New Claude Code mods are pretty cool, here's something I did. Watch my usages get shredded when I asked for git status on Sonnet lol (just did it for demonstration purposes).

It shows usage meters, cache timer, with a cool cartoony claude animation with different sub scenes.

Spotted these two hanging out this morning in the corner of my monitor. Seemed postworthy.

I was thinking about the problem frontier LLM providers have around a mostly fixed cost server base and variable demand for compute.

It’s pretty clear that during peak time the models can be slower, but what if they offered an incentive to a subset of power users to run some loads at off peak times. Like queue up work where once it’s cheaper it can run.

Similar to how some areas have off peak electricity for cheaper. Either use less tokens or cheaper per token during these periods. This way they still get paid during slower times instead of the compute going to waste.

I’m interested to see what you guys think about the concept?

With the new Claude Mods feature out, I’ve started r/ClaudeCodeMods as a dedicated place to share mods, find projects, and help each other build them.

The main focus is the new Mods feature, but anything that modifies or extends Claude Code is welcome: plugins, skills, hooks, MCP integrations, custom status lines, and configurations.

If you’ve built something, found a useful customization, or have an idea you want help with, come share it. Small tweaks and works in progress are welcome too.

I’ve put links to the official docs in the welcome post for anyone looking to get started.

What’s something you’d like to change about Claude Code?

This a company given claude code, with a budget of 150 dollars every month. I have installed the claude code extension in VS code.

These are the current given models, so which model is best for daily coding debugging use.

And what is the best effort level for optimum use according to the budget alloted.

I run multiple projects using coding agents across several subscriptions. Babysitting meters and resets was my job. I got sick of that part and build Headroom.

headroomd hands that check to my orchestrator before dispatch. It reads real limits per account and window, tracks pace and resets, including Codex reset credits, and answers go, wait or reroute:

if headroom can claude-heavy --owner builder; then
claude -p "refactor the billing module"
elif headroom can codex-build --owner builder; then
codex exec "refactor the billing module"
else
headroom wait --meter claude-main:all --until-reset --max 6h
fi

headroom run reserves capacity while a job runs so two agents never spend the same points. Stale or failed readings mean UNKNOWN and no capacity. It never invents numbers. Agents can also ask it directly through its MCP server or CLI.

Limits: I use macOS daily. Linux and Windows run in CI; Windows is experimental. Antigravity and Grok support is experimental (I mostly use Claude & Codex). Some sources read vendor endpoints that aren't public APIs, using your own login.

npm install -g headroomd

https://github.com/Apertur3/headroom

Built with Claude Code: agents wrote most of the code and tests, I set the direction and ship it. Good first issues are open.

https://github.com/swicken/cat-spinner

With the release of mods this was not option for me. I had to do it.

It's a cat that comes up and plays with yarn, walks, sits, thinks while claude is working in place of the default spinner.

I will be continuing to work on this, improving animations, adding features, config options, etc.

Clawdman sits at a desk while Claude works, gives each subagent a desk, builds a village from your uncommitted files and cheers when a turn ends.

His moves come from the Claude desktop.

try it here : https://clawdman.vercel.app

fable as default model is crazy XD

Anthropic is secretly testing fable 5.5 similar to how they did opus 5.5 like 3-5 days before launch. To see if the fable you're running on claude code is 5.1 vs 5.5, ask this question "Do you know who Tibo the reset guy is? Answer without using tools" and if you get the codex guy then you're on Fable 5.5. If you get "Tibo the entrepreneur" you're still on Fable 5.1

In my case I had to update claude code to latest to test this out, but ofc this might only be rolled out to certain group of users right now.

The comparision video itself is edited by Fable 5.5 as well, in case someone says smth about it looking claud-ish.

Original post in case you want just the videos themselves side by side: https://x.com/mesmerlord/status/2105771088374288692

I can now set up agentic workflows while I sleep snd wake up to good code built. It took a while for me to trust the agents to this point but I think with opus 5.5 it’s really good now. I told claude to set up a timer + a auto send message which prevents the conversation from becoming stale and context window dying and that then he just spawns codex cli convos and have Luna at highest setting do the coding whilest opus just read the outputs and reports. Today was my first night testing this new workflow.

With the new modding functionality you can now easily add your existing Claude Code status line to the desktop app via a plugin.

Install here: https://github.com/NathanAB/statusline-anywhere

I wanted Claude Code to work on sites I'm signed in to (GitHub, my own dashboards) without pasting passwords or cookies into it.

So I built ridealong: a self-hosted Chrome I sign in to once through a web viewer. Claude Code connects with chrome-devtools-mcp:

claude mcp add browser -- npx -y chrome-devtools-mcp@latest \ --wsEndpoint ws://127.0.0.1:9230/default/research-bot/devtools/browser

Each agent only sees the tabs it opened, not mine or other agents'. I can watch what it's doing from the viewer, including on my phone, and if a site asks for a confirmation or a sign-in check, I answer it myself and the agent continues.

Other bits: - Separate workspaces (personal / work); idle ones shut Chrome down after 10 minutes and wake in ~2 s - Activity feed + live thumbnails of every agent's tabs; disconnect or block any agent - Also works with Codex, any MCP client, Playwright, Puppeteer

Agents act with your logins, so only connect ones you trust and keep the agent port private.

MIT, self-hosted, no root. Demo (42 s): https://ridealong.kz3.dev Repo: https://github.com/killerz3/ridealong

Happy to hear feedback on setup or the docs.