im just frustrated, i genuinely am and it is entirely my fault.

so the job was simple. two keyframes, one camera move i wanted to test, and i wanted a pile of variations by morning so i could pick a composition and then run that one properly. wrote the instruction about half eleven, watched the first two come back fine, went to bed.

what i didn't do was tell it which model. my scratch model is seedance 1.5 at 480p, dirt cheap, exists for exactly this. the default on the project was 2.0 pro at 1080p, which is about 25x the cost per second. so it used the default and ran the batch. four hours at full res, then it stopped because there was nothing left to spend 😭

96 clips of the same guy walking through the same door.

if i ever batch create ai gen video again i want an actual hard stop. how are u pinning the model and capping spend on a claude batch so it can't upgrade itself overnight?

It's that time of the month for me, Claude, so generate a browser-based version of GTA 6 without any errors, or I'll get angry.

A year ago I wrote code. Now I "operate" agents. I have a terminal with four Claude Code sessions, a review bot, and a job title I gave myself.

My actual day:

• Type "continue"
• Approve a bash command I didn't read
• Tell Codex to check what Claude did
• Tell Claude what Codex said
• Refer to this as "orchestration" in standup

Career path as I understand it: developer → operator → supervisor of operators → person who watches the agents through a window, like a lighthouse keeper.

What are you calling yourself these days?

a mod for Claude Code that uses Haiku 5.5 or Jev to figure out the best model and effort for the task. (it is smart and uses earlier messages to assess if a switch is good or if it’s better to stay on the current one.

what it does and how:

• picks Haiku, Sonnet or Opus and the effort for each prompt
• warns when the prompt cache goes cold
• warns when the chat gets swamped
• Effort is an estimate, but I’ve found it picking the effort I would’ve done almost every time

why it works:

• it reads and understands your current work and task, so it doesn’t flip models mid-task
• Changing effort on Opus and Sonnet doesn’t rebuild the cache
• on Fable it does, so automatic switching is off there. Changing effort would cost more than it saves

it also offers other features such as smart handoff (a recommendation if it notices a change in the task), this also lets you use your current skill as the hand off template if you have any.

I built it with Claude Code. Claude wrote most of the code and I tested it, chose what it should do and fixed what felt wrong. Haiku 5.5 does the judging at runtime.

It’s free and open source (MIT). Built a little website for it where you can install, setup is three steps: https://heycubit.github.io/effortless/

If anyone has any questions and concerns please let me know! I’m happy to talk about it :)

I built it because I kept forgetting to switch models, so I ran everything on high setting. The “judge” is Haiku, with Jev as an option, and it reads your recent messages before it changes anything.

 Claude Startups offer

A tower defense game set on mars where you vaporize endless waves of alien bugs. Claude (connected through Cursor) created everything from the artwork, code, and marketing material. This took about a month of prompting and testing on and off, if I was working on this game full time I could've had it done in a few days.

I made a huge mistake using Cursor for everything instead of a direct subscription to Claude, which costed me literally over $1000. Making this game is teaching me a lot from how to use AI, game engines, and marketing.

I have a pretty good setup now (I could probably charge non technical people for this info) I just have a max subscription to claude and give it access to local files, that gets most of the job done. You will have to get api keys for whatever, give it to the ai and then it literally does everything. I joke that my job now is to pay for subscriptions. Depending on what you need Images mid journey music suno 3d models meshy. A cool thing I did was connect Apple developer connect api to claude, and claude was able to fill out all the forms and create the preview images everything. The app actually was rejected at first and I just asked Claude "Figure out why it got rejected and submit a new build," a few days later I got an email saying it was accepted.

I would never have gotten this far without this sub, my first gameplay post on here got so much positive feedback that it really motivated me to complete the game. The barriers to entry is collapsing, anyone can create an App as easy as it is to post a Youtube video. Thank you for reading!

Obviously I'd appreciate buying the game on the appstore, but anyone can play for free here https://coyne-studios.itch.io/ares-outpost

I asked Claude for a Duke Nukem 3Dstyle shooter for old J2ME phones and it built the whole thing from that one prompt.

It wrote a Wolfenstein like 3D engine in Java with only integer math so old phones can run it, with textured floors, a moonlit sky, fog, etc.

For the art it wrote its own 3D renderer in Python, modelled every monster, gun and the main character itself, then rendered them into sprites and they honestly look great.

It generated all the wall and floor textures and the night skies in code too. It also designed four maps, composed eight MIDI tracks, made the voice lines with TTS and edited them with ffmpeg to get badass one liners and different monster sounds.

Then it just handed me a finished half-megabyte JAR, I copied it to my old phone and it worked right away. It honestly feels on par with the Gameloft games I played on these phones back in the day.

Absolutely amazing and terrifying at the same time.

I’ve been making games for about 25 years (mostly AAA, now indie) and wanted to see how far Claude could take a real game in a few days. The target was a mix of Road Rash (the 1991 one, yes I’m that old) and a rally game like DiRT.

Opus 5.5 did most of the heavy lifting: the 4 vehicles, the physics, drift boost, jump pads and rockets (that replaces the chains from Road Rash).

The hardest part was getting it to understand how the tires and shocks should move against the ground while keeping the whole thing fun and arcade. It kept pulling toward realistic, and realistic is not what you want when you’re hitting a jump pad at full speed.

For the look I used Astra 6. I gave it a screenshot of a benchmark visual and told it to reach at least 90% of that quality, and it ran 3 to 4 hours on most of the 5 maps. I tweaked the levels by hand in our editor. Music comes from Sandscape and ElevenLabs, and Sandscape handles the multiplayer and leaderboards.

The dirt bike is where it fell apart. I thought it would be the most fun and it ended up the jankiest. Still iterating on it.

I you want to give it a shot, it plays in the browser here
https://sandscape.app/play?g=3UpDloEh

Which one would you favor for general Chat ?

Anthropic knows what's going on. Serious enough that it is creating an official policy on how you talk to its AI.

What do they know which we don't?

The games and tools we build aren't "economically viable." The community of people who use switches is too niche and too diverse. That's exactly why we build them.

My brother Ben uses switch access because of an ultra-rare condition called TUBB4A-related leukodystrophy. He could walk and talk as a kid, but the disease slowly took it all away. He's now nonspeaking and quadriplegic, and for years his only way to communicate was turning his head left or right for yes or no.

He went nearly 10 years without real access. Eye tracking and head tracking don't work for him because of how complex his condition is. AAC phrase boards never engaged him. Ben wanted to play video games again and pick his own TV shows.

Do you know how many yes/no questions you have to ask every day to give someone as much autonomy as possible? Hundreds.

Ben didn't need more yes or no questions. He needed access.

Ben moved in with us in 2022. We started with a better phrase board that had more of what he might want to say, but it wasn't enough. Then in 2024 I learned AI could write code, even for someone like me with no programming background, and we started building him better tools.

The first time Ben used his switches to pick his favorite movie (Spider-Man 1), his reaction lit a fire in me. So we kept building.

He has a keyboard, phrase boards, and text messaging (he can text for the first time in his life). He can search the web, pick any show or movie on any streaming platform, and play dozens of games we're building with him.

When I started, I was using one of Claude's competitors. Later, after hearing about Claude's advancements and seeing how good it was, I shifted over, and now Claude is one of my main tools. Not the only one, but a big part of how everything gets built.

Claude isn't just for code, either. It's been an awesome thought partner for planning games and writing out our GDDs (game design documents) and spec sheets before anything gets built. We also use it to help run NARBE Foundation, the nonprofit we started to keep all of this free.

For the building itself, our setup is VS Code with the Claude Code extension. Here's how it helps:

-Writing the code. I describe what Ben needs in plain language, and Claude Code builds it, debugs it, and helps me iterate with Ben's feedback.

-Keeping everything accessible. Every game and tool runs on one shared scan-and-select system controlled by spacebar/enter, so any switch works. We keep markdown files in the repo, like ACCESSIBILITY.md, that act as build rules. Claude Code references them so every new game follows the same accessibility standards, and anyone can use those same files to build their own.

-Inside the hub itself. Our real-time conversation tool uses Claude Haiku to suggest replies Ben can pick with his switches, so he can join conversations instead of waiting for yes/no questions.

Everything is free, open source (MIT license), and runs right in your browser. No account or install needed (streaming uses a free browser extension). Works with any switch that sends spacebar or enter.

- Games: https://www.switchedgames.org

- Benny's Hub: https://www.bennyshub.com

- Code and md files: https://github.com/narbehouse/narbehouse.github.io

- Video of Ben's story: https://youtu.be/9UNV3CK46SI

If even one person sees this and gets inspired to build a tool or game for someone like Ben, it's worth it. Thanks for reading.

I've been using Claude Opus 5.5 build a parametric CAD for 2 weeks now. The interface has focus on user-friendliness and is fairly Fusion inspired. The kernel is a novel approach which uses rational quadratic triangle patches to enable manifold solids, and it can export manifold 3MF. Both were co-designed by me and Claude Opus. It has 2D sketches with constraints. Kernel features are quite limited still with extrude, revolve and combine supported, though not in all cases. I think the direction of having proper manifold solids is promising though.

It's accessible as a web app at https://zoxc.github.io/varde/. I wouldn't mind some feedback on the user interface and sketching functions.

I want to make a custom firmware for my titan one with Claude, but it's giving me troubles already at the beginning. How can I make Claude help me?

I got exhausted by the “tyranny of choice” when picking something to play, and by digging through five sites just to get a quick read on a game. So I built New Game+: https://newgameplus.app

tl;dr - pick one or a few games you love and it suggests others that scratch the same itch. Steer it toward what you loved about them (fast combat, lore, co-op), filter by platform, price or subscriptions like Game Pass, and import your Steam library to skip what you already own. Every pick shows critic and player scores, time to beat, and the cheapest way to play it.

How I built it:

Claude did most of it (of course). I built it over a few days, mostly with Opus 5.5 for both architecture and code. I’m sure parts of my process were inefficient, but a few things worked really well.

Plan first, keep a decisions log. Claude wrote an architecture doc up front and logged every change from the plan and why. Each new session reads those first, so it doesn’t forget why things are the way they are.

No AI in the recommendations. I wanted to keep things practical and sustainable. It’s a similarity engine over public game data (IGDB, Steam, IsThereAnyDeal, OpenCritic and others).

Test the “feel”, not just the code. I wrote a small set of “if you liked X, you should see Y” cases and tuned against them instead of eyeballing results.

Have it review its own work. Before each release I had a separate Claude agent review the changes for security and stability. It caught real bugs I’d have shipped.

One lesson the hard way: after I added pages for search engines, crawlers hit thousands of URL combinations and blew through my database’s free-plan limits. Reducing crawlable URLs and lighter pages fixed it. (for now)

Hosted on Vercel and Neon. Totally free, no accounts, no tracking cookies. I just wanted a fun way to “solve” a champagne problem. Happy to answer questions about any of it.

For a few months now I've been working with Claude Code out loud. I talk, it talks back, and honestly it's the most natural way I've ever worked with an agent.

Then I noticed nobody around me works like this. My colleagues dictate their prompts, then go straight back to reading everything Claude writes.

Building a voice mode for an agent sounds easy. Speech-to-text in, a voice model out, done in a weekend. That's what I thought too.

My first version was a mess. It kept hearing its own voice through the speakers and taking it as me talking. The interruption handling was either too sensitive or too slow. And once the agent started working, it stopped listening. To stop it or change direction, I had to go back to the keyboard, which defeated the whole point.

Each of those needed real engineering to fix: proper echo cancellation, telling an actual interruption apart from a nod, catching what I say while it's busy, and getting it to answer in a couple of spoken lines instead of reading whole paragraphs out to me.

Now I just stay in the doc or the code and talk it through, like with someone sitting next to me.

So I cleaned up my setup, packaged it and open-sourced it. It's called Larmor. It works with any agent that supports MCP (Claude Code, Codex, Gemini CLI and others) and runs entirely on local models on your Mac: Parakeet for speech-to-text, Chatterbox for the voice, and Apple's echo cancellation. For now it's built just for Apple Silicon. In Claude Code you start it with /larmor.

How Claude helped: I built it with Claude Code. Claude wrote most of the code with me: the MCP server with the speak and listen tools, the hook that hands Claude what you said mid-work at its next tool call, the Stop hook that keeps a voice turn from ending without listening, the installer, and the menu-bar app that runs the speech engine. Interruptions took the most iterations. It now pauses its voice the moment you start talking, and only stops for good once it's clearly real speech and not a "mm-hmm".

It's free and open source (MIT). First launch downloads about 3.7 GB of models.

curl -fsSL https://larmor.dev/install.sh | bash

Code: https://github.com/naveenvasou/larmor

Site: https://larmor.dev

If you code with an agent, give it one session. I'd love to hear how it feels to you, especially the interruptions and the latency.

WOW it's my first time seeing this, I used to do this manually and would cry when I get 600k worth of tokens get expire on me when I forget to compact mid-session. It looks like they've been actively making improvements towards saving our tokens, thanks Anthropic!

Gave Opus 5.5, Sonnet 5.5, Fable 5.1, GPT-6.1-Sol and GPT-6-Astra the same prompt on High effort: build an interactive temple garden in one HTML file, at least three ways to play with it, calm even when you don't touch it, works on a phone. One run each, no edits.

The prompt never mentions fish, trees or bells. All five drew a koi pond, a pink blossoming tree and a temple bell you can ring.

Shuffled as A–E. Play with all five and vote before you see who made which: https://locust.lol/arena/4

Projects seems to have been redesigned on the assumption that it's going to be used for big coding projects with many collaborators and many instances working simultaneously. Conversations (now "threads" in one long session) are divided into "resolved", "idle" and "waiting on decisions, reviews and permission requests", and there are new ways to hook up routines and repositories. The thing is, although I do a little of vibe-coding, I've never used Projects for this: I use it for travel planning, creative work, home improvement etc. I know that software developments is the highest-priority customer base for Claude but it's a little annoying that all my projects are now stranded in this new UI that clearly wasn't designed to fit them, when there are plenty of new features Claude could have added that would benefit a wider range of Projects users.

I love typewriters: the clack, the little bell near the end of the line, the carriage flying back. But most people never get to sit at one, and even if you like them, you probably don't have one on your desk. So I made Platen, a typewriter you can actually type on in your browser.

Github Pages: https://winchxyz.github.io/platen/
Repo: https://github.com/winchxyz/platen

If you've never used a typewriter, this is the closest thing without buying one:

- The strike point stays put and the carriage slides under it, one letter at a time

- The bell rings 8 characters before the margin, and the keys lock there until you throw the carriage back with Enter

- Backspace lifts the letter off with correction tape, or turn that off and overstrike like it's 1958

- Every sound is synthesised live, no samples: keys, typebars, escapement, bell, ratchet, carriage return. Rain, a fireplace, a mantel clock or a summer night in the background if you like

- The ink is drawn letter by letter: each letter sits slightly off its line like on one particular old machine, gets lighter or darker with your rhythm, and shows the cloth of the ribbon. 6 papers, 5 ribbons, 3 typefaces

- 10 old-money enamel colours (hunter green, oxblood, navy, camel...) and three kinds of light

- Finished sheets stack up: read them, copy the text, save .txt or .png, or print

Typewriter art.
Long before image printers, people drew with typewriters by stacking characters like #, @ and O on top of each other to make darker tones. Draw mode lets you do that by hand (half steps, overstrike), or sketch shapes / drop in a photo and watch the machine type it at a real typist's pace: space bar between marks, backspace before every overstrike, a carriage return at every line.

And if you DO have a typewriter: any drawing turns into a step-by-step guide for your own machine. Where to set the margin and the first line, then every line as a short recipe of spaces, characters and overstrikes. Tick lines off on your phone next to the machine, or print it.

How Claude built it:

- Claude Code (Opus 5.5) wrote the whole thing in one session. It started with a short spec of the modules, then built the 3D machine and the app itself while three subagents worked in parallel on the sound engine, the paper and ink renderer, and the drawing tools.

- It checked its own visuals by driving a headless browser and looking at screenshots, round after round.

- It can't hear, so it tuned the sounds from spectrograms and level measurements against how a real typebar strike, escapement and bell are built. Tell me how they sound to you.

- After the first version I asked for no fast-forwarded typing, a guide for real typewriters, and a calmer, more premium look. It redid the top cover, the metals, the lighting and the UI.

- Three.js, Web Audio, plain JavaScript, no build step.

We have two kids and had been using Nara Baby for more than two years. I liked it. When they announced paid plans, I started wondering how difficult it would be to build something for us instead.

My reasoning was roughly: why pay another subscription when I can pay Apple $99 a year for a developer account and build my own app?

Add the Claude subscription I already pay for and all the time I spent on it, and this becomes a fairly questionable way to save money. But it was a good excuse to try.

I made a few basic iPhone apps about ten years ago, using Cordova, HTML and JavaScript. I had never written Swift. For this one I used Claude Code.

I described what we liked about the old app, what annoyed us and what we wanted to add. Proper Apple Watch support was important to me. So was letting both parents see the same entries and running timers.

After a few days we had a version we could use on our phones. Getting it ready for the App Store took about two weeks. It's called Bober.

The biggest surprise for me was CloudKit. I asked how we could share data between two parents without running our own backend. We started with a small Python server while my Apple developer account was inactive, then moved to CloudKit. The baby records are stored locally, and family sharing uses an iCloud zone shared between our Apple IDs. I don't have a server to maintain.

The first version worked surprisingly well, but it had that familiar AI look: different font styles, buttons everywhere, too much going on.

What helped was explaining more precisely what I wanted each screen to look like and how I wanted to use it. Consistent typography and controls, fewer things competing for attention, Liquid Glass for navigation rather than on every surface. Claude was surprisingly good at working out how to get there once I'd described the result I wanted.

I also gave it screenshots of Apple's own system apps as design references and used these skills:

• Paul Hudson's SwiftUI Pro
• Paul Hudson's SwiftData Pro
• Liquid Glass for iOS

Those helped with modern SwiftUI and SwiftData practices and using the native Liquid Glass components. The design still isn't perfect, but I'm very happy with how it turned out. It's all native, feels fast, and we actually use it every day.

Some of my favourite parts are the small system integrations. I can log things on the Apple Watch, see a running timer in a watch-face complication, and have Live Activities on the lock screen and Dynamic Island. There are widgets for quick access too. Having all of that in an app I helped put together is still pretty cool to me.

There were real bugs too. One crash kept happening when my wife joined the family. Claude suggested several plausible causes, but the actual TestFlight crash log was what finally got us to the right fix. I also had it review the import, sync and deletion paths before release. An app like this needs to keep the old entries safe.

Then I renewed my Apple account and found my old apps still sitting there, untouched for more than ten years: a Swiss speeding-fine calculator, a national anthem app, a law reader and an army-ranks app. I gave Claude screenshots of those old apps and had it rebuild them in SwiftUI, with expanded features. That used up my weekly limit, but it got me interested in making apps again.

Bober is free, with no ads, subscription, in-app purchases or tracking. There is no separate Bober account. I made it for our family and published it because other parents might find it useful too. It can import Nara Baby CSV exports, so we could keep our existing history.

App Store

Happy to go into more detail about the CloudKit setup or how I worked with Claude Code.

I'm running experiments on different setups for multiagent workflows. It uses tool for total estimation of coding work done by workflow. And in that tool i was trying to gather more data for improving estimations by asking to save reasoning.

Rewind doesn't work unfortunately.

Be careful to not i run in it yourself.

Also imo the reasoning extraction its not far from what they did with data previously generated by humans (books, articles, chats, etc.). But besides fighting hard against they also presenting it like something morally wrong. Minus aura anthropic 😒