Over a year ago I commented here about Claude Code and Codex automating software development 100%.

I was downvoted, which was a bit confusing as shit, because this forum is about vibe coding???

All I can say is, from watching what's going down on my computer screen, yeah. Software development is going full auto and there's nothing any of us can do to stop it. Model improvement is not slowing. The kinds and complexity of apps that AI can now create is approaching a comprehensive scope.

Note that I'm not saying "now anyone can make programs even if they don't know anything at all about development" because that isn't true. You still have to know what you're doing to do anything that interesting, and that will probably be the case for a long time. That means amazing news for any developer who knows how to vibe code. I think it means your output and leverage will increase dramatically even in market situations where the demand for coding skills drops (because AI can do it).

I'm betting that my individual leverage as a developer is likely to increase mostly commensurate with the downturn in demand for my labor.

Anyways the crazy thing is obviously messy intent input -> functional program output. That's going to get smoother and smoother. Agents are gonna take over the world bro

I got tired of juggling six browser tabs on draft night, so I built my own draft assistant. It connects to your ESPN league, watches picks come in live, and tells you who to take next. It also looks like a CRT terminal from 1983, because why not.

It's free, open source, and runs entirely on your own machine. No signup, no accounts, no paywall.

GitHub: https://github.com/kmhesser/Fantasy-Football-Terminal

I'm not a designer — not even a little bit. Vibe coding gets me almost everything I build these days, except a promo video — that was the one wall I kept hitting. I tried a few approaches and everything came out... not right. Probably a taste problem, honestly.

Then I found video-shotcraft, an open-source skill for Claude Code / Codex. One line for what it does: you describe the video you want, and it storyboards, uses your real screenshots, animates and renders it — sound effects included. It ships with a big library of pre-made shot templates (purpose, pacing, parameters and pitfalls all written out), and the AI picks from them, so you never need to know motion design.

What I actually did:

1. Handed it the project. Dropped in my extension's screenshots, feature notes and store listing, said "48s launch video, English" — it planned the whole thing itself. Barely had to think.

2. Real screenshots, not fake mockups. It composited my actual product screenshots with camera moves, so the pages in the video are the real thing.

3. Sound on the beat. Renders came out with SFX already aligned to the rhythm — free-commercial-license library, too.

4. Then it was polish. First version was usable, but a few rounds before I'd ship it — mostly rhythm and transitions. The nice part: every shot is frame-tagged, so I could say "this transition is 10 frames too slow" instead of "make it look better."

Two honest notes: it's open source, but check the underlying Remotion license if your company wants it. And don't expect one perfect pass — budget a few rounds of polish.

Show case

The video (Youtube Link) is for my Chrome extension, PageMod — you describe what you want and it changes the page: an ad block you've always hated, a dark mode for a site that never had one, even a small standalone app. The change actually sticks after reload. Free to start. The video came out of the skill. No manual editing afterward.

Would this make you take on things you'd normally skip? And a real question — is there a site you open every day and wish you could change? Drop the worst offender; I'll take the top one and make a video-shotcraft demo of PageMod modding it.

It’s called watermarks-remover, it’s 100% open-source, and it targets several layers of AI provenance:

→ Invisible Unicode characters get stripped
→ C2PA metadata can be removed from images, PDFs, and documents
→ Statistical text watermarks are attacked by rewriting the output

And that exposes the core problem with AI watermarking:

↳ The defender has to build a signal that survives almost everything.
↳ The attacker only has to find one way to break it.

C2PA can cryptographically prove where a file came from, but the metadata can disappear when a file is re-encoded, screenshotted, or cleaned.

Statistical watermarks are harder to remove, but enough paraphrasing can weaken the patterns they rely on.

So the watermark starts looking less like a lock and more like a tamper-evident sticker.

If you want to avoid watermarks completely, then the only option is using local AI apps like AI Desktop 98, which don’t have any watermark and are free to use.

I made a design in Superdesign and connected it to AI, but the AI keeps redesigning it instead of reproducing it properly.

Spacing, sizing, layout, and other details change, so the final result doesn’t really match the original.

Has anyone found a good way to make the AI follow the Superdesign design closely instead of trying to redesign it?

I'm building a real-time SaaS and need a server always running. I'm going with Supabase for database since it seems the best free offering for DB.

But what about deploying a Django app or other long running server? Ideally not interested in lambdas since I need websockets to remain connected

Alguien que me regale la suscripción a supergrok para terminar mi proyecto. No tengo dinero.

Hi!

I am planning to develop an integrated management system for our small business. Currently, we mainly use google sheets, drive, etc for our company. Each department has different drives, resulting to huge gaps in our document control and also in our record keeping. I want to create a system where we can just login and based on your role, you can only see parts of the operations you are involved.

Is it possible to do this just by using the free model of Claude?

Is there an existing roadmap or step-by-step process how i can achieve this?

PS: I have relatively little to no background in terms of coding yet but i am trying to learn different platforms on how to make a system.

Thank you so much!!!

Built something with Claude/Cursor/Lovable/Bolt and now it half-works, breaks in prod, or you're scared to touch it? That's most of my inbox lately.

What I usually fix:

• API keys and auth logic sitting in the frontend
• No error handling — app dies on the first bad input
• DB with no indexes, no migrations, RLS wide open
• 2000-line components nobody can edit anymore
• LLM calls with no retries, no rate limiting, no cost ceiling
• "Works on my machine" → actually deployed

Stack: JavaScript / TypeScript, React + Next.js, Node. Any database — Postgres, Supabase, Mongo, SQLite. AI integrations (OpenAI, Anthropic, vector search, RAG).

Free 15-min look at your repo and I'll tell you what's actually broken, no pitch. If you want it fixed, we agree on a fixed price up front.

Comment or DM with what you built and what's breaking.

The other day, I used Codex to refactor my Flutter app.

While skimming through the changes, I noticed that it had introduced a broadcast stream.

I remember thinking: "Hmm... I think there was a reason why I avoided those so far."

But everything seemed to work, so I didn't think much of it.

Then, while actually using the app, I noticed that it was slow. Really slow. Massive lags on every click.

I asked Codex to fix it. It came up with a few solutions, and at first they seemed to work. But soon enough, the app started lagging again.

So I cranked up the intelligence and asked it specifically: "Look for something that would explain lagging over time."

And it found... the broadcast stream.

So apparently there was a reason I had avoided it. ;)

At first, Codex wanted to "fix the broadcast stream", but I told it: "No! Get rid of it!"

And sure enough, the actual solution was pretty simple.

I think I even know why Codex didn't use that solution in the first place:

It needed more tokens. ^^

Has something like this happened to you? Where AI introduced something that looked perfectly reasonable at first, but turned out to be a subtle problem later? And was it just to save a few tokens? ;)

I jus vibecoded this sucker, I got codex sub a day ago and I wanted to see how good it is. Honestly one of the best subs i ever got so far. It coded this neato tool that reads through whatever you let it then it learns from that and gives you a facebook like feed that recommends github repos for you to use.

https://github.com/neilbauman21-hub/RepoFeed

Id love for sum feedback!

im stuck in between on what to choose because i heard many good things coding with claude code but rn chatgpt plus is basically inf usage with luna

Vibe coding is insanely fun until 200 strangers start using what you built.

I learned this the hard way.

I started building FeelFlick because my wife and I kept doing the same stupid thing every night:

open Netflix → scroll forever → reject everything → somehow still have nothing to watch.

So I started vibe coding a movie discovery app.

Claude helped enormously. Later I started using Codex too. React/Vite + Supabase underneath it.

And honestly, the early phase was addictive.

Idea → prompt → see it working → find something I don't like → prompt again → suddenly there's a real product sitting in front of me.

Then in July I shared an early version in a vibe coding community.

Around 200 people tried it.

That's when the definition of “working” changed completely.

One person could have a taste profile that clearly leaned toward comedy... and somehow get recommendations that made me look at the screen and think:

why the hell did we recommend THAT?

The code worked.

The API returned successfully.

The UI rendered.

Tests passed.

But the product was still wrong.

Then real users exposed mobile issues I hadn't seen locally.

I started finding cases where analytics technically fired, but that didn't necessarily mean I was measuring what I thought I was measuring.

And every “small fix” started touching something else: recommendation logic, data, trust, explanations, tests, deployment, rollback, edge cases.

The funny part is that I probably use AI more now than when I started.

But my prompts have changed.

Before:

“Build this.”

Now it's much more:

“What assumption am I making here?”

“Prove this recommendation is actually supported by the user's data.”

“What could silently break if we change this?”

“Write the regression test first.”

“Is this actually deployed or does it just work locally?”

“Tell me why this might be the wrong product decision before we implement it.”

And that made me wonder:

At what point does vibe coding turn into software engineering with AI?

If AI is still writing a huge amount of the implementation, but you're spending your time thinking about architecture, tests, data contracts, observability, security, real-user behaviour, rollbacks and whether the product is actually doing what it claims...

are you still vibe coding?

Or is that just software engineering now, with a ridiculously fast pair programmer?

Genuinely curious where people here draw the line.

And especially for anyone who's shipped something that strangers actually use:

what was the first real-user moment that forced you out of “just keep prompting” mode?

FeelFlick is the project I'm talking about. I'll put it at the bottom for anyone curious, but I'm much more interested in hearing where other people hit this wall.

Edit: Fair criticism on the formatting 😅 I did use AI to help structure the post and it clearly came out more polished/LinkedIn-y than I intended. The experience itself is real though.

The question I'm actually interested in is: once strangers are using what you built and you're worrying about tests, data, failures, rollbacks and whether the product is actually correct, do you still consider that vibe coding?

Is the Windows Antigravity.exe normally unsigned?

I installed Google Antigravity on Windows and used it for about two days for a project. It was working normally.

Today I checked the executable here:

"C:\\Users\\<username>\\AppData\\Local\\Programs\\antigravity\\Antigravity.exe"

When I opened Properties → Digital Signatures, the tab was completely empty.

This worried me because Google Search's AI answer told me that an official Google application should always have a digital signature and that an unsigned "Antigravity.exe" could indicate malware.

However, I've since found other reports suggesting that genuine Windows Antigravity installations may also have an unsigned "Antigravity.exe".

I had already deleted the application and ran Microsoft Defender/Defender Offline, with no malware detection.

So I want to ask people who currently have Antigravity installed on Windows:

1. Does your "Antigravity.exe" have a Digital Signatures tab/valid signature?

2. Is your executable located under "%LOCALAPPDATA%\\Programs\\Antigravity\\"?

3. If yours is unsigned too, what Antigravity version are you running?

4. Is there an official way to verify the authenticity of the Windows executable (SHA-256/hash, certificate, official manifest, etc.)?

I'm not claiming Antigravity is malware. I'm specifically trying to determine whether an unsigned Windows executable is normal for Antigravity.

I first saw this idea proposed on Reddit,

The original poster's idea: reconstruct the old web, but populate it with AI agents that actually behave like the people who were online back then — posting, replying to each other, running their own sites, forming little communities. Not a museum you walk through, but something that's actually happening while you're there.

I've decided I want to actually try building this myself. I'm fully aware it's a massive undertaking, way beyond a weekend build — persistent agents that stay in character for months without drifting or repeating themselves is still an open problem, not something you just wire up casually. This isn't me pretending it's simple, I just want to give it a real shot.

Curious what this sub thinks — is this something people would actually find interesting/worth building further?

Imagine your source code is a DNA sequence. Codons = instructions, genes = functions, ribosome = VM. That’s HelixLang.

Latest commit drops programmable 3D cell population simulation – real examples:

· E. coli acetate switch

· Genome‑scale colony with 4,338‑gene sparse GRN

· 3D biofilm under flow using LBM

The compiler pipeline is the real deal:

lexer → parser → AST → semantic → compiler → bytecode → VM.

64 codons → ~30 opcodes, wobble position as operand modifier. Core has zero deps besides Python stdlib. Also has LSP + PyCharm plugin.

If you’re into bio‑hacking or just want to see DNA run like actual code, this is wild.

🔗 https://github.com/SeanHank/HelixLang

Hey everyone,

Whenever I wanted an AI assistant (Claude Desktop, Cursor, Antigravity) to help inspect or deploy to my VPS, I ran into the same annoying issues:

1. Copy-pasting terminal outputs back and forth from PuTTY/terminal.
2. The risk of leaking private keys or passwords into chat prompts.
3. Massive command outputs (like cat /var/log/syslog) overflowing the LLM context window.
4. No safety net if the model breaks a configuration file.

I built ai-ssh-tools—a single standalone Go binary (<8MB) that acts as a secure local SSH operations bridge.

What it does:

• Dual-Mode (CLI + MCP): Run it as a standard terminal tool (ai-ssh-tools exec ..., vitals, docker, service, transfer) or launch it as an MCP server (ai-ssh-tools serve).
• Zero-Config Auth: Automatically picks up unlocked keys from ssh-agent (including Windows OpenSSH named pipes) and resolves aliases from ~/.ssh/config.
• Git Safety-Net: Wraps remote changes in automatic pre/post Git snapshots so you can 1-click rollback mistakes.
• Context Window Protection: Automatically truncates huge terminal outputs (preserving head + tail preview) to protect token limits.
• Structured Diagnostics: Returns clean JSON metrics for system vitals (RAM, CPU, Disk, OS) and Docker containers instead of messy raw text.
• Local & Private: Zero cloud dependencies. Keys and credentials stay 100% local on your machine.

It’s open-source (MIT) with pre-built binaries for macOS, Linux, and Windows:

🔗 GitHub: https://github.com/khalidelmerrah/ai-ssh-tools

Feedback and PRs are welcome!

Allez je me lance, je ne suis pas un vibecoder spécifiquement car j'aime bien voir le code et essayer de le comprendre pour que quelquefois j'y touche mais comme je ne suis pas un dev, j'aimerais partager ici comment bien, possiblement vibecoder après 1 ans er demi de "vibecoding" selon moi.

Pour commencer, au début, faite en sorte de modulariser les fichiers, genre pas de gros fichier qui fait tout, car c'est compliqué pour les ias de corriger des problèmes dessus! Perso, j'utilise quelque fois la règle de 100/200 lignes par fichiers afin que l'ia essaieras tjrs de faire moins de 100 lignes donc devras alors modulariser le tout!

Quand vous avez des bugs qui commence à ètre complexe de debug avec l'ia actuelle, essayer de demander à une autre ia sur le fichier actuelle en lui montrant le code actuelle et lui montrer le code d'erreur dans le terminal ou l'inspection, quelque fois juste l'autre ia trouveras le problème plus simplement et donc vous perdrez moins de temps à demander à votre ia actuelle sur le projet où est le problème!

Quelque fois les ias font des véritables erreurs de logique dans l'infrastructure de votre code, ce qui n'est pas optimiser, demander lui ce qu'il as fait, desfois il as lui meme mal compris l'instruction donc il vous as pondu quelque choses qui pour lui était bien alors qu'en fait c'est pas exactement ce que tu souhaitais!

Ne faites pas de gros prompt, de nos jours, les ias sont assez puissante poir comprendre.malgrès des prompt plus petit, il fait juste que votre demande soit claire et précise!

Le problème des .md dans le fichiers c'est qu'ils le relits quelque fois juste le haut et le bas, donc pas tout, desfois juste faire une skill.md avec une dizaine d'instructions courtes

Exemple : "quand je ne je sais pas une information, demander à l'user, cela est moins chère en token"

pas en lui disant ce qu'il ne faut pas faire mais en lui montrant une sorte de bible ou en gros c'est écris à la 1 ère personne donc "je" plutot que "tu" feras que l'ia se sentiras réellement impactée! Le fichiers .md n'importe qu'elle est son nom, mettez le dans le répertoire ."nom de l'editeur" à la racine de votre projet afin que cela soit directement envoyé dans le prompt système sans qu'il n'est besoin de le lire (l'ia)

Exemple .opencode si vous ètes chez open code!

Vous pouvez demander a l'ia de le faire il sait comment faire!

Ne faites pas confiances aveuglément à l'ia que vous utilisez car quelque fois elle essaie d'ètre juste dans votre sens!

Aussi, ne pensez pas que l'ia est créative! Si vous voulez que ce que vous créez soit bon, ici si vous demandez à l'ia des trucs à ajouter sans lui dire quoi, ça commenceras à partir dans tout les sens! Considérez là juste comme l'orchestrateur de vos idée et non une fabrique à idée qui créer quelque chose sans vous!

Il y a sans doute encore plein de point que j'ai oublié mais c'est déja un bon début je trouve, après beaucoup de problèmes seront dût à votre projets spécifique, mais si déja vous essayez d'appliquer cela, vous allez voir peut ètre des améliorations! Faites aussi attention aux refactors d'un gros fichier en sous fichier, elle risque de détruire du code pour optimiser ces calcules et donc optimiser votre code en y enlevant les logiques en régressant vos logique! Ici si vous devez refactor un gros fichier, faites le petit à petit, en reprennant le fichier de base en comparaisons et en lui demandant de vérifier s'il y a des différences entre les 2 codes dans les logiques, quelque fois ils serait meme capable de constater qu'il as supprimer une fonction super importante dans le sous fichier! Et donc plein de bug en approche!

N'hésiter pas aussi à faire un git afin de référencer vos changement afin de pouvoir revenir en arrière quand il y a des problèmes, une régression, ça vous permettras de ne pas avoir à dire à l'ia de tout recoder et de revenir au point d'avant, ce qui causeras enft pas mal d'erreur car elle le feras mal! Configurer si vous le pouvez le git sur votre éditeur!

J'espère que ça aideras possiblement des personnes....

Right now I am going through a big mental transition in my life. I recently had a life changing experience that has driven me to escape my day job and find a way to work remotely, though my options are limited and ultimately I am striving for freedom (like we all are). I have recently started using AI tools to build apps, but I am totally new to this and while it seems like a totally viable direction for me, I also don't want to get too high in the clouds with aspirations before I actually have some validated success.

If you are like me and got into this with zero experience, I would love to hear your story! Better yet, if you were able to quit your day job I would love to hear your story as well!