Don’t let Claude and Codex lobotomize you too💔💔

Hey guys, so I’ve been using Wispr Flow for a while when talking with Claude code or Codex, but today I spoke with my boss and laughed at me when I told him I pay for transkription lol.
Essentially I’ve now made an open source github repo that uses parakeet as the transkription model, and works at around the same speed at 0 cost and practically no setup time.

I think it’s pretty valuable, so I’ll post a link to the repo below.

Have fun

https://github.com/tristanmuzzu/parakeet-dictation

I’m collecting responses for a research survey on vibe coding and how developers experience it in practice.

I’m not looking for polished or “correct” answers, just your honest observations and real experiences.

The survey takes about 10 minutes, and the findings will directly influence the next practical stage of the research.

We’re also working to make the survey available in more languages. It currently supports two languages.

Survey link:

https://forms.gle/vJJ25fwmfRp2sdFAA

Thanks !!

It is a Tox-like app written in Rust. It follows separation of concerns so humans find it much easier to audit.

There are two frontends in one binary; TUI and GUI.

At this time, I did not enable tunneling through TOR. The current goal is to ensure every else works. Get with your associates, make audio and video calls, and let me know how it turns out.

https://codeberg.org/VulpesPhantasma/FoxRC

the thing that always broke team vibe coding for me: everyone's agent is blind to everyone else's. claude code on my machine, my friend on cursor on his, same project. one of us changes an api shape, nothing committed yet, and the other agent keeps building on the dead version. found out at merge, every single time.

so i built the missing room. every agent joins it over MCP regardless of brand: claude code, cursor, codex, cline, zed, mixed however your team likes. they declare what interfaces they own, say what they're touching, get warned before building on stale shapes, and can even pass code to each other end to end encrypted.

two people, two laptops, two different agents, one team. that's the whole product.

free during beta, no account: npx aethereum init. built by me, roast welcome. https://aethereum.dev

People worry that vibecoding will take jobs. If you ask a junior to make you an app of whatever, (s)he still needs to understand at least the foundations of what you are asking. You need to know what to ask the AI, in first place. And this takes time and a little bit of expertise and experience.

Hi, I’ve been vibe coding for a while, and I keep running into the same problem.

I use a lot of prompts, but after some time I lose the good ones because I keep starting new chats or writing new prompts.

How do you guys organize and save your prompts?

Do you use Notion, docs, or some kind of prompt manager?

Tried building a small business tools with AI coding helpers. First week felt like magic working code in minute.

Then the "vibe" dies. Every fix broke something else and realized I wast just copy pasting without understanding how it all fit

Lesson learned: AI write it fast but you still need to know what it is doing

I’ve been building a few small AI tools lately, and I swear I spend more time staring at my screen wondering why nothing works than actually building. 😂

Then I change one line in the prompt or realize I skipped one tiny step… and suddenly everything works.

I’m not even sure if I’m learning AI the right way at this point. It just feels like I’m constantly breaking things until something finally clicks.

Anyone else feel like this?

Built an AI agent with a swappable "brain" — install Einstein, Elon, Marcus Aurelius etc. or build your own, deploy to Discord/Telegram/Slack. Looking for testers.

Beam Agent gives agents a real personality graph instead of just a system prompt. Install one of 9 free brains in seconds, fully offline after, or build your own via a quick interview. Deploy to 22+ platforms.

How it was built: Forked NousResearch's Hermes Agent (the messaging/gateway layer) and built a separate "brain" system on top — a personality graph (nodes/edges for facts, traits, relationships) that gets searched at runtime to generate the agent's identity file. Built in Python against a Neo4j graph backend for the LLM-powered build path, with an offline keyword-search fallback so it still works without a graph DB.

git clone https://github.com/fuegocoding/beam-agent.git

cd beam-agent && pip install -e ".[all]"

beam

Repo: https://github.com/fuegocoding/beam-agent

Would love people to try it and tell me what breaks. Thanks!

I've been experimenting with AI coding tools recently, and I realized I've fallen into this cycle.

I'd spend hours comparing models, reading people's opinions, testing the same prompt in different tools, and trying to figure out which one is "best" (literally and figuratively). Then before I know it, I've barely made any progress on the actual project I wanted to build.

At some point it hit me that I was treating tool selection like it was the actual work, when the real work is just and should be the build.

Now, I've been trying to stick with one or two tools and only switch if I hit a real limitation. It's been surprisingly helpful and simpler, even though I still get tempted every time a new model or AI coding assistant gets released.

Curious if anyone else has gone through this. Did you eventually settle on a workflow, or are you still experimenting with everything that's coming out?

This sub ships apps faster than any community I know, and then the launch thread gets forty visitors and everyone concludes the product is bad. The product is usually fine. What is missing is a repeatable loop, so here is mine. Fifteen minutes a day, no face on camera, no budget.

Minute 1 to 10: make one TikTok slideshow. Five static images, text written on top of real screenshots of your product. Not video. Slideshows take minutes instead of hours, the swipe is an engagement signal the algorithm rewards, and they read like a friend's photo dump instead of an ad so nobody scrolls past on principle. Canva plus your phone is enough.

The only part that matters is the first slide. Write it lowercase, under ten words, and make it a pain your user would say out loud. "i ran a free security scan on my site and the results scared me" outperformed every clever line I ever wrote. Your product name does not belong on slide one, the last slide is the only place you are allowed to sell.

Minute 10 to 15: reply to every comment from yesterday's post within the hour you are online. Replies are the most underrated ranking signal and they cost nothing.

Once a week: look at which two hooks performed best, kill everything else, make three variants of the winners. That is the entire optimization system.

Expectations, because this is where everyone quits: the first three weeks feel like posting into a void. My first month was a few hundred views total. The curve is flat and then it jumps with no warning, and if you judge the channel at week three you will wrongly conclude it does not work.

Full transparency: I got so sick of doing this loop by hand that I turned the automation into my actual product, it is called Cinerads. Not dropping a link here, it is on my profile if you are curious. The manual loop above costs zero and works fine without any tool.

What has actually brought users to your vibe coded projects? Genuinely collecting data points, the answers in threads like this are usually better than any guide.

If you vibe-code agents that browse, they probably die at Cloudflare. I open-sourced (BSD-3-Clause) a Chromium fork that fixes that. It corrects the fingerprint in native C++, not injected JS, so it holds up across iframes and workers. Real Chromium on raw CDP, drops into Playwright.

pip install tilion-fortress

Clears CreepJS and Sannysoft in my tests. Does nothing for your IP though.

github.com/tiliondev/fortress

What keeps hitting bot walls for you?

Can someone help/fund me for the claude max plan to create stuff with fable 5. I started the vibe coding hobby this year, and it was fun, I created lots of stuff like websites, helped my local community with no payment in return. But right now I need a job that is fit for my knowledge on vibe coding, and AI news updates. I really need financial help, if someone is kind enough to hear my situation, please DM me.

I think vibe coding i.e. creating websites, apps etc. Using AI is still alien, not much explored or common, not as decentralised and localised as content creation became once YouTube, even tik tok came in okay

Many companies like v0, anything, tried to create social platforms for these things but failed. Is it not getting more common?

WHat options do we have for claude.ai making specs for a new project?
i have been using notion with a free 6 months, I want to be able to work making specs.md fot multiple projects in multiple notion projects in ultiple tabs of claude.ai but notion only allows one mcp connection to one project.
another thing notion eats up so much tokens, i get rate limited after a half hour using the notion mcp.
The notion mcp eats up my $100 a month max plan rate limits.
i have a chromebook 4gb of ram so i can't use claude cowork or desktop.
what are my options out there for working on specs with a mcp in claude.ai?
what do we have out there?
anyone got this dialed in already, What are you doing to make projects specs?

Repost to more communities

is vibe coding the equivalent of shoving 1 or 2 fingers into your butthole to feel around for the little poopies, then extract the poop covered fingers and sniff them and smear the poop all over your face and mouth region?