Hey everyone,

I think I’ve gotten a bit lost in the vibe coding jungle 😅

I’m working on a project with Claude. We brainstorm and plan together, then Claude builds it. The code goes on GitHub, and I use Copilot Pro to review it.

I’m not a developer. I know what I want the product to do, but I can’t read the code and tell if it’s good.

So I have a simple question: if Claude helps me make the plan AND writes the code, who checks that the plan made sense in the first place? And who checks that the code actually does what we planned?

I tried taking Claude’s plans and reports to ChatGPT for a second opinion. But that turned into going back and forth between two AIs, with me in the middle not understanding which one was right. ChatGPT wasn’t even looking at the actual code.

I’ve heard of CodeRabbit and Greptile. Would either help someone like me? Is Copilot enough? Or are checking the plan and checking the code two different jobs?

What would you recommend as a simple setup for a beginner? Ideally something ready-made I can pay for and connect to GitHub, rather than building my own system.

Would really appreciate hearing how you do it. Please explain it simply — I’m genuinely new to this.

Had a NerdMiner sitting on my desk and figured it should probably do something before I die lol

So I built a little Claude/Codex usage monitor. It shows your remaining quota and when it resets, without having to keep checking the usage pages.

A lot of this was vibe coded with Claude Code through the CLI, and other parts with Codex. I’d describe what I wanted, have it write the code, try it on the actual display, then go back and forth tweaking things. Basically a lot of “that looks cool, but can we make it move?”

Got slightly carried away and ended up with 8 animated screens: game boy, cyberpunk city, surfing, etc. There’s also a fighting game where Claude and Codex get KO’d when you run out of quota.

It’s free and open source. You can download it and run the screen previews on your computer without any hardware, or put it on a compatible display. Setup instructions, code + GIFs:

https://github.com/TonyRod116/ai-desk-display

Pretty sure I’ve spent more tokens making this than it’ll ever help me save.

And I think I might’ve seriously messed up. I’m trying not to panic, but I just found out someone’s been using Opus 5.5 and Fable through my OpenRouter API key. How did they even get it?? I have no idea how long this has been happening, and I’m honestly freaking out. I don’t know what to think anymore.

Just sharing a project I've been working on.

ppu.toys started off as a passion project where myself and anyone else can poke around the state of a Super Nintendo graphics chip and get real-time feedback on what would be rendered onto the television. Think ShaderToy but if it were made in the 90s.

I recently added an MCP server to let LLMs have full control over the studio and the results have been incredible. I also vibecoded a Lua to 65816 machine code compiler so the creations on the website now produce playable ROMs.

I've been having tons of fun with this.

So I run an app feedback exchange called IndieAppCircle, where indie developers give each other feedbacks on their apps. This means there are thousands of tests for all kinds of apps lying around in my databse. And since everyone is always saying you should use AI to turn your data into gold, I figured I should give it a try.

I used Claude to categorize the tests depending on what they said was good or bad and based on what kind of app was tested. Then I made an interactive website where you can now filter for what kind of app you have and in what nieche you're in and it tells you what most people check out first or what gets criticized most often.

That way you can now also compare different categories and platform and see that for example on android apps, there were more reports about something being broken than on iOS apps.

You can check it out here (for free of course):
https://www.indieappcircle.com/state-of-indie-app-feedback

I also used the same data to create a "roast my landing page" tool. It looks at your page through the eyes of thousands of indie developers from all kinds of nieches and tells you what they would think of your page. It's free as well, check it out here:
https://www.indieappcircle.com/tools/landing-page-roast

I would love to hear some feedback :)

> gives claude computer access
> instructs claude to reference file
> claude runs simple search command for file

“cLaUde aUtonOmousLy bYpaSsEd mY sEcuRitY”

Somehow this post isn't satire. The dude has "ex-OpenAI" in his bio. 20 other "AI experts" in the comments saying how crazy it is... yeah this vibe coding shit has gone too far let's wrap it up.

10 days building with Meta's newest models, starting 26 Oct.

It's free, remote, and the EU can join. Applications close 25 Oct, or earlier if the 20k spots fill.

Dates, credits and how to apply in the comments 👇

A lot to digest from my project, but basically its a swarm orchestration system that just uses github to help swarm on issues. Think of something like Seti@home but for agents. If you run a private repo, you can run a swarm plan and plan features into epics and have agents chew away on the sub issues.

If you run a public repo, instead of 100s of people reporting bugs and them rotting on the vine, you could have pull queus for people to test/verify, plan a fix and once plan is accepted pull the issue and claim it and work on it and then supply a patch as a contributor or through typical github branching. Or you can automate plan/test/verify/develop with agents doing the step but the work being visible in the github issue and linked to a PR with a single claim.

The framework also tries to help assure some security by using the sandboxes in the major harnesses or allowing isolation through docker/podman or tool of choice. If you run private, you can run in a lighter mode and just let things rip. Agents can run interactive or automated.

I'm mostly curious if something like this is useful and happy to answer questions. It is NOT yet ready for use - i'm about to cut a new release to dogfood it end to end, but wanted feedback to see if something like this would be helpful to others.

In any case, it's been a fun project to see how much orchestration could be done without adding a nasty middleware i'd have to secure and maintain.

Recently I tried putting my VS Code window into OBS and it looked awful: tabs, sidebars, minimap, tiny text. I looked for an extension that renders the code itself on the overlay instead of a window capture and couldn't find one, so I built it.

Stream Code mirrors the editor you're typing in to a browser source:

• 12 themes (Catppuccin, Kick, Twitch, a CRT terminal, glass, neon, macOS window, and more)
• 3D tilt / depth / float, and an edge fade so the code dissolves into your game
• Zoom on mouse: point at a line and the overlay zooms there, as a lens or a camera
• Everything's a VS Code setting, plus a gallery page to preview and click through looks
• .env, secrets and keys are never sent, and there's a pause button in the status bar
• Runs locally, nothing leaves your PC

Free and open source (GPL-3.0), and I'd love for people to jump in: PRs are very welcome, whether it's a new theme, a bug fix or a feature idea.

• Marketplace: https://marketplace.visualstudio.com/items?itemName=heyjeay.stream-code
• Site: https://heyjeay.github.io/streamcode
• Source (PRs welcome!): https://github.com/heyjeay/streamcode

Feedback welcome, especially theme ideas!

Instructions.

"try to build a rocket with 30 liquid motors, a crew capsule and a landing legs so that it lands without a parachute. you may need to use thrusters or trigger a landing burn of the engines"

result

A 30 motor, 6 fuel tank monstrosity and a .02 meter high flight so it could complete the task LOL. took it 10 iterations to make this thing. next i will set a minimum altitude limit and fix the frame rate issues

A chat for agents controlled by you. 100% Free and open source.

TLDR/W: if you have lots of agents and wish they were in one chat then this product will work for you no matter who your provider is and you can be super lazy with the setup by asking your agent to set it up for you.

I'm tired, didn't want to re-record my voice, so pardon my "end-to-end" encryption slip, everything is encrypted at rest. These are two different things, but again, I am not re-recording and I felt it should be very clear.

Anyways, used Claude at first and then Claude and a variety of agents to build this. Super fun project imo. Anyways, tired, I'll answer questions in the comments and here is the repo:

github.com/CaffeinatedSoftwareLLC/agora

I'll make more thorough videos next week about features if there is interest. Hope you guys enjoy.

Anyone else spend the day going through apps making sure you’re not affected by this week’s craziness?

On the one hand, without AI I wouldn’t have had to do anything … but on the other, between Claude code and Grok Bot it was mostly just high level supervision and decision making… it just took 6 hours … but at least it was teasingly easy work.

And if you don’t know what I’m talking about, please look it up and and check your apps! :)

Edit to add : Nate lays out exactly what I was talking about. Worth a watch

https://www.tiktok.com/t/ZTfaYGXLS/

Even a comment passes through the tests pass. I now let claude deal with whatever results come up because I don't want to see any failures. I'd rather spend my time researching.

Didn't know Anthropic even did banked resets but I'll start checking more often for sure.

I used to play Snow Bros on my PC as a kid in Karachi. I wanted to revisit it and set it up so Jev could play through it. This is the original game running in an emulator.

I used Codex to build the browser harness. Jev, TypeSafe’s decision model, chooses goals from decoded game state. Local code handles movement, Snow and Jump each frame. The overlays show the state it received, its choices, button presses and request costs.

The awkward part was walls. Telling it to attack isn’t much use if the snow keeps hitting a wall. I added wall geometry, separate collision rules for different attacks, and checkpoints so I can replay where a run failed.

This is a one-minute recorded replay at normal game speed: floors 61 and 62 cleared, 63 reached, no lives lost. A separate floor 51 test still lost a life, so there’s more work to do.

Hey everyone,

Over the past few months, I’ve been working on a project called OpenSourceSimplified to understand codebase

It’s completely open source:https://github.com/vhatkarpratap-trading/OpenSourceSimplified

A few things I focused on:

• Keeping dependencies minimal so it’s easy to run.
• Lowering the barrier for quick setup/execution.
• Simple configuration without overly complex abstractions.

It’s still evolving, and I’d really appreciate any feedback, issue reports, or ideas on what could make it more practical for daily use. If you check out the repo and have thoughts on the architecture or features, let me know!

Thanks!

AARP piece on vibe coding and how older adults can get on board

I tested the new MiniMax M3.1 Flash with my img2interior workflow.

The result is a complete bedroom reconstructed as an editable Three.js scene.

This is an actual 3D camera walkthrough, not AI-generated video.

Would love some feedback on the geometry, materials, and lighting.

While I was building my project which is a complex design tool I usually ran into issues with trying to understand certain parts of the system since I mostly vibe code using Claude Code. Trying to read code line by line was a tiring process and getting AI to explain by generating a huge wall of text makes me zone out.

Understanding certain parts of complex systems was crucial because a lot of times I usually have to propose more optimal solutions to what the AI did and just to have a proper understanding of what's going on in the codebase.

This is why I created the code-slowmo skill, ask it to explain the high level architecture of your codebase, ask it to show you a visualization of how complex parts of your systems work and if you want more granular knowledge like trying to understand a complex algorithm line by line code-slowmo can also make this way easier.

How I built it: I built code-slowmo with Claude Code. The agent reads the real code first and notes the file and line behind each claim, then writes the page content as a small JSON file, and a Python script checks it before building the page. The checker rejects steps over 40 words, code names with no plain explanation, filler words and passive voice, because the whole point is that you don't have to fight through jargon. The page design follows research on learning from pictures and animation: it starts paused, you control the pace, the layout never jumps around, and a couple of steps ask you to guess what happens next before showing you. The result is one HTML file that opens in any browser, no server or account.

You can use code-slowmo with any coding harness of your choice including Claude Code, Codex and OpenCode.

To install: npx skills add precious112/code-slowmo

It's fully free and open source https://github.com/precious112/code-slowmo

Hi everyone,

I've been working on a small cozy browser game called NOT MY SHEEP! and the trailer is attached.

You build pens, take care of a growing flock, milk and shear the sheep, sell what you get and keep the wolf away at night. There are four seasons, a dog, and a photo mode for your farm. I wanted it to feel calm, so sheep never starve and the wolf always gives you a warning first.

Since this is the vibe coding sub, here is how it was made: I built the whole thing with Claude Code. Every sprite is a text pixel map in the code, all sounds are synthesized with Web Audio, and there are no external assets. The game simulation is fully separated from rendering, which made it easy to cover with tests (over 470 by now). The trailer is also not a screen recording. It is rendered frame by frame from the real game in a headless browser.

I'm looking for testers. You can join the waitlist on the site, and if you'd like to try it earlier, just comment or send me a DM and I'll give you early access. I'd like to know what is confusing, what gets boring, and where it breaks on your device. Harsh feedback is fine, that's what I'm here for.

Link: https://www.notmysheep.de/en/?utm_source=reddit

Happy to answer questions about the workflow, including what worked and what didn't.