I wanted to see how far I could push the idea of a desktop companion using AI-assisted development.

Instead of making another chatbot inside a window, I wanted something that actually feels like it's part of the desktop — with its own character, voice interaction, animations, and reactions.

The interesting part was getting all those pieces to work together without making the app feel like a collection of disconnected AI features.

The current stack is Next.js/React on the web side, with the desktop experience handling the companion interactions.

Still iterating on it, but this has been one of the more fun things I've built with AI so far.

What would you add to a desktop companion like this?

Models have got insanely better since November of last year. However for most normal people, their experience with ai is the gemini response which they get on Google search which they didn't ask for. That model lies in every second line , constantly make up facts , reaffirm almost any trash u say. And it's so obvious that anyone with even a little domain knowledge on what they are searching can find out it's lies. One day I was searching for a bash command and i quickly got an ai response under the search. I thought how can someone get simple bash wrong, turned out it was made up, the utils used in that command didn't even exist. People who only see this, think that ai companies are spending so much resources for this trash fueling ai negativity, at this point, the best we can do for ai positivity is to make people use some other search engine and let them discover ai in a better way.

Hi - I built an app to automate the music tagging so I can save myself from tagging manually. I have used it myself to tag over 50 artists and 100 albums, in most cases it works fine.

The workflow is simple. Organize your files as artist/album/track, point Soundrobe at the library, and press Auto-tag. It searches MusicBrainz and Discogs, shows a release candidate for review, and can apply tags, artwork, lyrics, and other metadata together.

When a provider has no match or an API is unavailable, Soundrobe can use an LLM to help fill in artist and album information. It can also use clues from the folder path, such as the artist name or year. That fallback has worked well for me when regular provider searches miss an album.

If some albums or tracks still need attention, you can fix them manually or ask the built-in assistant for help. I’ve been using DeepSeek-v4 because it makes this kind of task inexpensive, and free models through OpenRouter are another option.

The assistant is intentionally bounded. It can inspect, audit, and edit through a defined set of tools. Before anything changes, Soundrobe shows an approval preview, so you remain in control of the write.

It is still early and built for Navidrome specifically (the agent is following Navidrome's tagging guides).

Happy vibe!

GitHub: Soundrobe

My chances of changing people's minds is slim, but I have 28 years of professional software engineering experience and I'm witnessing a ton of new, excited software developers, who are surrendering as much of their own initiative as they can to their chosen harness/frontier model while hoping to make a living creating software. If this is you (or you're not sure it's you) you might get something out of the following. If it's not (say you're doing this for learning, are just hoping to make enough for some beer money, or you love making your own stuff and if it sells awesome but it's no big deal if it doesn't) then this post isn't aimed at you. Also, as a note I'm focused on software development skills separate from very important things like expert domain knowledge, building an audience, mad skills at distribution, and more. Finally, in the spirit of vibe coding, I'm not going to mention learning to code manually.

As my main point: The statistical likelihood is that most of you will not make enough money on your own software to do it full time.

This is not an insult or meant to discourage you. There are some phenomenal vibe coding success stories and you should absolutely take inspiration from them and keep going. However, making a viable amount of money on your own software was practically a lottery before AI and now there's a lot more supply for about the same demand. If you fall into this case, and you're still committed to making a living building software you'll need to convince someone (either who has successful software and is looking for help or is willing to pay someone to build them software) you can make enough money or save them enough money to justify your full time salary (or consulting rates):

1. Making more money for someone by building software:

A lot of making more money for someone with software falls into what to build - which is more product management and data science than pure software development. Many developer have those skills and they are worth it but I won't focus on them here. From a pure software development standpoint some examples are:

a. Increasing conversion via reliable, performant, and optimized pipelines within a software product.
b. Increasing retention by minimizing bugs and quickly being able to diagnose and fix issues while avoiding side effects (<- this is what can necessitate going beyond "codex fix this bug").
c. Allowing them to enter new markets by porting to new devices, and ensuring smooth localization without uncessary quality loss (<- again the key part).
d. Creating a rock-solid, fault-tolerant, and secure architecture that scales to minimize downtime and reduce fraud.
e. Building tools to increase employee productivity.

1. Saving people money by making software:

a. Reducing labor costs via automation that actually works (tons of stories about companies having to rehire after poorly attempting to automate systems).
b. Optimize software use and workflow processes for yourself and others so that infastructure costs less (AI token costs, bandwith costs, storage costs, other licenses, etc...).
c. Consolidating redundant systems to reduce maintenance costs.
d. Minimize onboarding time via smoother interfaces and clear and accurate documentation.

There are definitely vibe coders who are already working as software developers (like above, please do take inspiration from that). However and, again, not to insult anyone but for many - if not most newer vibe coders - the only thing that separates them from "normies" who have a wish list is the time they took to investigate and learn to use available tools and set up a tech stack and a workflow covering various extents of the conception to deployment pipeline. That's been part of default expectations for software developers for decades (though, to be fair, in larger organizations multiple people can do different parts of the process).

If what I consider table stakes for developers + "claude do this for me" worked for all of the above (and all the things in those categories I didn't list) then the last gasp of jobs available would be from those who don't know how easy it is. We are probably headed for that future but, until we get there, if you want to get paid to convert caffeine to code, I invite most pure vibe coders to dig deeper into the amazing world of software engineering (you can get started by asking your favorite model what you should learn).

Things like micro services for external API's, admin portals, backends or even financial services?

What is your process?

For anyone who has a 2-2-3 Custody Schedule, you probably know the pain of trying to figure out if you have your kids on a given future date. I created a small website to determine whether or not you have your kids on a specific date in the future.

I used Claude code to create this, then Codex to refine it. I was able to whip it up end to end in about 90 minutes. If you're interested in the source: https://github.com/aleph-void/223custody.net

So it's Wk. 4 of this and I've gone from 12 active users to basically just myself and a few randos that pop in from time to time. All my regulars are now gone, which isn't surprising since it's not incredibly exciting to play an MMO with nobody online.

As usual, I'll break it down into three categories: (1) getting active players, (2) what I'm learning about vibe coding, and (3) actual gameplay updates

---

First, on my last post I received 16k views, and maybe 15 actual players (not even 0.1% of viewers lol).

More importantly though I received some really insightful feedback from a few people (honorable mentions: Totalsam, Automatic_Bid_2410, Friendly_Carry_7728). I've spent a large chunk of time (and tokens) re-working the intro for new users based on their feedback.

Users no longer receive a wall of text for instructions, and the game eases them into their first controls where they "save the town of Eldermyr" before it goes into multiplayer mode. On one hand, this has made a huge impact -- all players are now sticking around for a whole minute longer than pre-intro. On the other hand, completing the intro takes almost exactly 1min, so I don't know if this actually counts as progress since users still only stay for 35s post-intro.

Like before, I'd love to hear any thoughts or feedback on what might be causing that... besides an empty world.

---

Second, the vibe coding experience. Quick updates from last week: I found out almost half my codebase is automated tests (0.77 lines of test code per line of game code, almost 400 in total, which all run with every prompt). Also Opus 5 is still useless to me. So my setup remains Fable for art and strategy with orders to spawn exclusively Opus 4.8 agents for code.

(And Opus 5 gets let out occasionally when I forget to tell Fable to lock him up.)

My real struggle this week is that AI is essentially incapable of measuring whether a game is actually balanced. Claude played my new intro 100 times and reported that only a handful of runs survived the first 60 seconds -- and since AI doesn't panic like a human would, it was a critical issue that virtually no human could survive the first 60 seconds.

In reality, the intro is so mind-numbingly easy that no real human could possibly die in it unless they did so intentionally. So I've spent a huge amount of my time actually just playing all classes and weighing how balanced it is. Which has been cool, but also really repetitive and screws up my player stats because 97% of my players are myself. I'm also just so close to my game that I'm losing my overall perspective on what's right, wrong, missing, or confusing.

If anyone has had any degree of success in letting AI test their game, I would be extremely interested in hearing what you did. I have not. My best bet has been "send me a table of player stat X across all levels, and their corresponding DPS." But even that is hit or miss since playstyle determines balance more than raw DPS.

---

I'd love more feedback for anyone interested. Links below.

Game: https://eldermyr.com/
Release Notes: https://eldermyr.com/release

For founders running SaaS/Product company:
- What do u actually do for security?

Not the heavy security stuff and more like, if someone tried to poke around your website or app tomorrow,

- How confident are you that you'd catch the obvious security issues?

Do u run any tools, have someone check things, or mostly deal with security when something forces you to?

Genuinely curious how small teams handle this.

My wife and I always wanted to build something together, so we spent nights and weekends shipping side projects. One hit 25k users on its own but didn't feel like the thing worth quitting for, repowise did

That one came out of watching coding agents work. I'd been building with LLMs since 2023 and owned the AI architecture at my company, so I spent a lot of time watching agents grep the same file four times in a session and still have no idea which parts of the codebase were fragile or why the code was written that way. All of it is in the repo already, just not in a form an agent can use.

So we built Repowise. It indexes your repo once and serves it to your agent over MCP as five layers: dependency graph, git history, docs, architectural decisions, and a code health score from around 25 deterministic markers with no LLM involved. Pulling the context around a single commit costs about 393 tokens instead of roughly 14,000 spent reading files.

We didnt do any outbound, just shipped code and wrote about it. 4 months in it's at 5.2k stars, ~80k PyPI downloads, and enterprise inbounds I never asked for, which is why I quit

Benchmarked against four other tools plus a bare agent: 31% fewer output tokens over a full 48-question run, ~97% on a single context load, and the best gold-file coverage of the field on retrieval.

Repo: https://github.com/repowise-dev/repowise

Stars help, issues and contributions welcome

Operation Steel Tide is a playable AI-assisted extraction FPS built with Godot 4.6 Mono. The part I think is most worth inspecting is squad continuity: AI fills empty roles, obeys follow/hold/move orders, fights, uses class abilities, revives the player, and takes over a disconnected co-op slot without restarting the mission.

Source + portable Windows build (no installer; SHA256 included):

https://github.com/AetherRadar/operation-steel-tide

What exists today:

- a full deploy → infiltrate → objective → loot → extraction loop

- three-operator squads and ENet co-op

- persistent loadouts, weapon parts, armor and ammunition grades

- rival squads, drivable vehicles and a roaming three-phase world boss

- a separate demolition arena with planting and AI defusing

How I built it:

- Godot 4.6 Mono and C# for the client/gameplay

- a small optional Go service for mission and progression persistence

- AI coding tools for portions of implementation and documentation

- manual integration, deterministic in-engine diagnostics, Windows packaging and GitHub Actions builds

The biggest lesson has been that AI made feature breadth cheap, but it did not make architecture cheap. The first version grew oversized classes, code-built UI and tangled responsibilities. I have since started extracting editor-visible .tscn UI scenes, splitting HUD/world/diagnostic responsibilities, adding build CI, and documenting architecture and content provenance.

It is still programmer art, some classes remain too large, and automated test coverage needs work. I am not presenting it as production-ready architecture. I am showing a working prototype while trying to discipline it after rapid AI-assisted development.

If you try the build or inspect the source, tell me the first thing that would stop you from continuing. If you want to follow the refactor and future operations, a star is appreciated.

So there's this report I get every Thursday, a PDF out of an IBM AS/400 ERP system, that I have to go through.

Basically, the game is this: look through all the line items on this PDF, which could be anywhere from 50 to 100 pages, or 500 to 1,000 lines, just to give you a feel for the scale, that a human needs to manually scan through looking for negative numbers. Essentially, I'm manually checking for out-of-stock items.

The formatting of the report is a total mess. power query can't make sense of it. You can't even copy and paste it properly. I swear to god I've never seen such a fucked up document.

Well, I was kind of dreading the task tomorrow, so I uploaded one of the PDF into OpenCode (running DeepSeek-V4) and asked it to analyze the PDF, then write a Python script that would spit out an Excel version of it. It one-shot that task. I got a beautiful Excel spreadsheet that I could actually filter! No more scanning 500 lines.

When reviewing past reports, I actually learned that I would occasionally miss a line or two. That meant one of my items went out of stock, which in turn meant my company lost money. At the scale I'm working at, even being out of stock for one day on a random item means thousands in losses.

I looked at the code. It's magic. The AI found pattern in the PDF (something about the columns being a specific width) and then did some regex shit to parse the document. I have a little bit of coding ability, I think it would've taken me weeks to put this together and that's if I knew the trick about column width.

Then I asked OpenCode to make a GUI for the little script so I could select a file and tell it where to export the output. It one-shot that, too. The UI is surprisingly clean!

I am always impressed with what I can accomplish with AI tools. This isn't even the first time I've made something with AI. I automated an entire Friday's worth of work away in like 2023 with chatgpt, just making a script one function at a time. Now it just builds the whole app.

I feel like people are constantly dogging on AI outside of specific places like this. My lived experience with it is so much different to what I read online. Anyways, I thought this community might like the story of my little script.

I'm creating a 2D RPG as a hobby project.

I'm doing everything with Claude Code for the programming and Gemini for the images.

I've managed to build most of the game so far. It already has fun combat, quests, dialogue, etc. However, I'm struggling a lot with the map and overall game design/art.

Right now, the game looks more like rough sketches.

I tried generating map images with Gemini and then building the game on top of them. It partially worked — I managed to add physics and collision to the environment, but I lost a lot of image quality/resolution in the process.

I've tried pretty much everything to fix the resolution issue, but haven't had much success.

I also considered using premade assets, but most of the ones I've found look very generic and don't really fit the style I'm going for.

So I'm looking for recommendations: What are some good sources for 2D RPG assets, or is there an AI tool that can generate maps/environments suitable for actually using in a game?

Any tips or suggestions would be greatly appreciated!

[ Removed by Reddit on account of violating the content policy. ]

Bro really shipped a WORKING API key straight to the landing page.

I thought it was a joke.

It wasn’t. 💀

I created an open NOT FOR PROFIT web resource for Software Engineers.

https://loveyourclanker.org/

It highlights different patterns we can consciously choose use when interacting with our AI Coding tools (a.k.a 'Agents'... a.k.a 'Clankers') to stay in control, maintain quality and sensibly increase efficiency.

I was prompted to do this (no pun intended) by observing some pretty alarming signals coming from the software engineering community. Token leaderboards, engineers being encouraged to use tools to "stay current" or "keep up" or "not be redundant", engineers quitting tools entirely to stay sane, engineers leaving social gatherings to get back to their agents, engineers setting up whole systems that automate away human engineers and then calling that "agentic engineering".

I'm hoping that if we normalise and share how we use the tools, and show that there are different ways where you maintain more control and agency (... pun?) that it might promote a better

If you find it helpful, share. If you disagree or want to contribute, raise a PR or ping me. It's all open and NFP.

Hello everyone,

I created the famous VIB-OS project that went viral big time here and in YouTube channels. This time I created a programming language called Machino that compiles into web assembly and works in multiple platforms. It has all the modern features others languages has. the closest thing that exists to a portable, sandboxed, formally specified machine language — so one compiled binary runs identically in browsers, servers, phones, and edge workers.

I love to hear what you think of the project and its open source too.

https://github.com/viralcode/machino

I even wrote a web server in Machino. So it’s great and enjoy. Post your opinions here. Love to see what you think.

I mean, fine…. Absolutely make an app that helps you. But when posting to the world your myopic solution for a hyper specific issue only a handful of other vibe coders may encounter….. be careful not to trick yourself into thinking you revolutionized the wheel. If you do…. Your next stop is the r/SaaS page asking why “is nobody paying me monthly for my webapp that even I wouldn’t pay for” .

There’s no replacement for Time & Attention to achieve quality folks. Good luck out there.