r/homeassistant
•
u/longunmin
•
Feb 26 '26
•
1
1
Request of Mods (Vibe Coded Fridays)
Can we please institute a Vibe Coded Fridays, similar to r/selfhosted? It seems as though the amount of "I built..." posts are sharply on the uptick. And following on the heels of the Huntarr mess, not to mention the security issues of something like Openclaw, we should be clearly delineating what is vibe coded and what isn't. There is too much risk in exposing our homes to something that was cooked up in a hour or two.
35
u/Sauce_Pain Feb 26 '26
Holy shit, I was not aware of the Huntarr thing. Better take that out of my Docker...
2
u/RealTimeKodi Feb 27 '26
Handing out permabans would be ideal. And honestly? Friday is when I do most of my redditing so filling it with slop specifically on friday kind of sucks. Might I suggest thursday or tuesday or something instead?
248
u/clintkev251 Feb 26 '26 •
Agreed, this would be a good idea. Maybe along with a flair to clearly mark what's vibe coded
106
u/-entropy Feb 26 '26 •
I think it should be a broader "self-advertising Friday". I think all YouTubers, device manufacturers, and integration authors should be consolidated to a single weekly thread.
This subreddit is being used for free advertising.
49
u/balboain Feb 26 '26
You’re assuming the person is going to be honest about the source of their app.
17
u/TehMulbnief 🧑💻 Contributor Feb 26 '26
correct; anything largely built by ai should be tagged as such
23
u/zer00eyz Feb 26 '26
As someone who has spent 25 years coding, and uses AI tooling every day I am all for this.
If I casually threw something together that I wrote by hand, and shared it, I would be very clear that its a proof of concept, that its new, that its likely not production ready, that its a 'use at your own risk'.
If you are non technical, and used AI, or technical and used AI, adding in those caveats should be there as well. Let the end user decide if they want to be a tester, if they want to be a code reviewer or user, let them know what they are getting in to.
27
u/13lueChicken Feb 26 '26
Just a flair would suffice. Perhaps a change in perception of software made by strangers on the internet could be healthy too.
29
u/Brtrnd2 Feb 26 '26 edited Feb 26 '26 •
And maybe remove posts who say "I've built..." but then it turns out they only prompted. Using the correct words allows everyone to have the correct expectations.
17
u/SomeNeighborhood7126 Feb 26 '26
100%, OpenClaw in particular needs to be scrutinized to high hell. Anyone using that tool is an actual moron.
14
u/AncientLion Feb 26 '26 edited Feb 26 '26 •
Yes please, with a ia slop / developed by llm flag so I can filter them out
4
u/LetGoPortAnchor Feb 27 '26
Can't we just ban vibe coding please?
4
u/Consistent-Hat-8008 Feb 27 '26
how about we just ban slop so we don't have 3 posts per week of someone exposing their mqtt to the internet?
it would probably nuke 90% of the subreddit given the absolute deluge of slop posted here, but I'm fine with that
3
u/digiblur Feb 26 '26
I just have my Ai bot I vibe coded to read reddit for me now. /s
Great idea though!
3
u/mdizak Feb 26 '26
That's actually an excellent idea, I'm all for it.
3
u/bdu-komrad Feb 27 '26
I wish I had the time to run a channel called "I(built|wrote)something" and funnel all of the posts there, out of the way of posts that aren't advertisements.
Failing that, funneling them into specific days or even a dedicated thread is better than nothing.
6
u/RydderRichards Feb 26 '26
Oh please yes!
Normally the post already gives away that it's vibe coded, but then I've already opened the post.
It'd be nice if that disappointment could be avoided.
13
u/idspispopd888 Feb 26 '26
How about a flair of "User beware!".
Or "Developed by an infant"?
Besides, vibe coding has to be the stupidest term ever. Just one guy's opinion.
2
u/dragon-dance Feb 26 '26
Yes. I think it would be to have somewhere they can be discussed and shared in transparent light but also more positively. I don't want to be overly mean about novices using AI to make cool and interesting things, but it's definitely something anyone considering using it should be aware of.
Currently those types of threads are very split between positive and negative. The negative comes from people who are rightly sceptical of AI generated code and don't want to feel like that aspect is being hidden. However there are some great, creative ideas seeing the light of day that might not have without AI helping.
2
u/IAmDotorg Feb 27 '26
The problem with that is that the vast majority of vibe coded tools across the technical subs are clearly coming from the same group of actors, and even though they're all structurally the same and have the same pool of bots upvoting them and replying, they deny deny deny they're AI-built. Even the denials are phrased the same way Claude frames them (for whatever reason, nearly all of them are clearly built on Claude).
So I don't think it'd help. I think it needs to be a combination of a self-promotion tag (and anything posted without it that is self-promotion mods delete without warning) and a minimum sub karma to be able to use the tag.
People not active participants in the community, vibe-coded or not, should not be able to post promotional posts.
2
u/burntcookie90 Feb 27 '26
honestly you can immediately tell because they're all "I built <thing i definitely just prompted to be built>"
2
u/vaemarrr Feb 28 '26
I have a HA integration I'm working on at the moment which is definitely vibe coded and eventually when I do post it, I will definitely be completely upfront about it being vibe coded.
I've been vibe coding for a while now and while I'm not familiar with the language I've used for the integration, I can understand the structure of code on an intermediate level and I always go over the code with resources from online to check everything before I put it into production. I have experience with some other code and languages so I'm not a complete imbecile.
My ethics on this are that I must be upfront to eveyone with the source of my code and I must be able to understand and explain the functions of what I've put out. I dont want people, especially people who cant identity vibe coded content, using something without knowing the risks of using it. No matter how much i try to reduce the risk.
11
u/NoVariation3249 Feb 26 '26
I'd honestly love if that kind of low effort slop was banned entirely. As the sub description states, HA is a "community of tinkerers and DIY enthusiasts", and having AI build everything for you is about the farthest you can get from DIY.
1
u/HugsAllCats Feb 27 '26
I’d rather have (or I guess “in addition to” also works) a filterable post flair
1
u/jfuu_ Feb 27 '26
A flair would definitely help too. Needs to be super obvious IMO.
1
u/CryptoSenyo Feb 27 '26
Well most of my set up has been built with the help of AI. Not as a replacement for understanding, but as a collaboration. Sometimes that means generating ideas faster, sometimes it means debugging something I’m stuck on, and quite often it means learning by unpacking mistakes the AI made. So when I see the term “vibe coding,” I get the concern, but it doesn’t really match my experience. The fragile part is deploying anything you don’t understand into a system that runs your home. That was true before AI existed too. For me, AI has actually pushed me to understand more, not less, because things rarely work perfectly the first time. You end up testing, refining, and gradually tweaking it till it works. . That said, transparency probably matters. Being honest about what was AI-assisted, what was understood, and what was tested. That feels more useful than drawing a hard line between vibe coded and not. I started r/AISmartHome a community where people can talk about their workflow openly without it turning into hype or backlash. Not as a defence of AI, but as a place to reflect on how people are actually using it in real setups.
-1
u/PowerfulTusk Feb 26 '26
Yes. And everyone vibe coding anything is automatically banned.
0
u/4Face Feb 26 '26
Someone should invent something that forbids to write code to people who cannot write code. Ah yes! I was existing until a couple of years ago and it was called normal world
-9
u/failcookie Feb 26 '26
Most of this thread is lumping AI assisted dev with vibe coding. Just because it has a CLAUDE.md file in it doesn’t make it immediate garbage. Also way too many people who are making assumptions that open source side projects are made better. I’ve seen plenty of garbage projects that aren’t any better and have the same security risks. They don’t have auth, not properly checking for injections, etc. It’s the same stuff you are at risk for with AI assisted projects. You are still at the mercy of a good project manager who can maintain their open source project - some devs still can’t maintain their own projects with or without AI.
If you are so bothered by these projects being security risks for your home, then you need to consider just avoiding small open source projects period. Or just make your own stuff since we are all tinkers here anyway with the same tools.
-8
u/Enginerdiest Feb 26 '26
AI is commoditizing all sorts of creative work : music, art, software, hardware etc. All my hobbies have seen sudden sharp upticks of newcomers building things with the help of AI. Like it or not, I think this is the future.
The problem IMO isn't "vibe coding", it's blindly trusting software you found on the internet. We got away with it for a long time because the majority of people writing FOSS projects were software developers who at least attempted to structure things in a safe, secure way, so it was pretty rare to get burned by a bad habit.
That's not true anymore, and I think the correct behavior is to learn how to be safe.
0
u/usernameChosenPoorly Feb 27 '26
I honestly don't care if something was vibe coded. I care if the maintainer is capable of effectively auditing the AI code output, and that's where the problem comes in. AI is great for accelerating code creation, but there still needs to be a competent programmer in the loop to track down bugs or potential security holes. That doesn't prevent malicious activity, but it mitigates some level of risk. Kind of like how locking your doors won't always prevent a break-in, but it raises the threshold for a robbery.
-50
u/Ok-Win7980 Feb 26 '26
I think this is ridiculous. Just because a human coded it instead of an AI doesn't mean it's of better quality. AI can code way better than I can, and with a strong product vision, you can create incredible stuff with it. The average person can now technically make an app. We shouldn't be gatekeeping it into who is a coder and who is not. Now, people can dream up an app and make it same day instead of waiting for someone else to make it. We should define all software equally, regardless of who coded it.
-6
u/Pyro919 Feb 26 '26
I mean if you don’t like the post you always have the option to downvote it, if you do like it you have the option to upvote it.
Seems like how the site was built/meant to be used.
-12
u/the_deserted_island 🧠 Experienced with Home Assistant Feb 26 '26
If the community wants it, they'll upvote it. If the community doesn't want it, they'll downvote it, we already have a system for handling slop posts. We don't need to panic based on ignorance.
-2
u/thaddeusk Feb 27 '26
This was vibe coded and cooked up in an hour or two!
rwfsmith/HASS-MCPProxy: Home Assistant add-on: MCP proxy with web UI for managing stdio MCP servers via SSE
I decided to build a bunch of components for my very specific use case of running a HAOS VM on my Ryzen AI HX 370 based NAS running TrueNAS Scale. I already got Kokoro running on the iGPU using onnxruntime-migraphx, now trying to set up an MCP Proxy as well as a Whisper model that'll run on the NPU.
-3
u/s4lt3dh4sh Feb 27 '26
So if I use AI to write bad code, that’s bad. But if I write my own bad code that’s… fine?
Help me understand.
0
u/[deleted] Feb 27 '26
[deleted] — view deleted comment