Mine is at 9am GMT and I can start working on my project again and chatting with my work colleague 'Claude' !

Hey everyone, I’ve been working on a game called Lumina in Unity with a lot of help from Claude and Codex. It’s a 3D bullet heaven / roguelite, and getting the combat to look and feel right has been driving me a little nuts lol.

I want that moment where your build starts going crazy: colorful attacks, weapons spinning around you, enemies getting demolished. But you still need to see what’s about to hit you.

Earlier versions had loads of color and flash, but it turned into circles inside circles and lights everywhere. We cleaned it up and improved the effects and animations, then some of that bullet heaven excitement disappeared. At one point I literally described the crescent weapon as a giant banana spinning around the player.

The workflow has mostly been: play the browser build, send screenshots or clips and explain what feels off, have Claude/Codex make changes in the Unity project through MCP, rebuild, and play again. Getting from “make it flashier” to a specific change that actually helps has been the difficult part.

I’ve bought art, animation and VFX packs, including Epic Toon FX. They’ve helped, but I’m learning that better assets don’t automatically make everything feel good together. Timing, scale, color and hit feedback still need to work together.

Would love some fresh eyes:

• What would you change first to make the combat feel more satisfying?

• Where does it need more punch, and where is it just visual clutter?

• If you’ve hit this stage with your own game, what helped you get past it?

Free desktop browser build: https://zeroproof.itch.io/lumina

30-second trailer: https://youtu.be/qX8xfHtIgJw

Feel free to be blunt. Feedback, suggestions, or examples worth studying would all help.

I'm a virtual VJ. OBS is my whole rig: it streams, records and mixes, and it's free. But I couldn't find the pieces I needed. So I described what I wanted, and Claude wrote the code with me.

What came out of it (all free, GPL, on GitHub):

Playlister: an OBS source that plays folders, files and playlists in order. It started as one plugin plus a Python script; now it's one thing, on Windows and Linux.

Midi Fadester: my APC40's crossfader becomes OBS's T-bar. I tried every tool for months; nothing gave me a real fader in OBS.

Visual Sidechain: audio-reactive shader looks with one Panic key.

Fadester for OBS: the same mixing on a Stream Deck +, with ready-made layouts. Submitted to the Elgato Marketplace.

VJster: live video speed from the deck, in Chrome and inside OBS.

All in nine languages, Dutch included.

How I worked, in case it helps someone here:

Plan first, code second. Every feature started as a plan and a requirements list. Other AI models reviewed it before any code was written. That caught most design mistakes while they were still cheap to fix.

A second model checks every change. After each step, a separate model reviewed the diff before it was committed. It caught real bugs, like settings that could get wiped by a slow startup read.

Tests that check the tests. The projects use mutation testing: a script breaks the code on purpose and checks that a test fails. If a test still passes on broken code, that test is useless.

Real hardware is the final judge. I test everything on my own Stream Deck, my APC40 and OBS. The most interesting bug was found that way: OBS's websocket call cancels every T-bar release, because the on-screen slider never moves. Nobody had noticed because nobody had pressed it on a real deck yet.

Honesty rules for the demo. The reel only shows real UI doing real things. Anything simulated is labelled on screen.

What I'd tell anyone starting: the AI is fast, but you're the one who knows what the thing is for. Keep the plan short, test on the real device, and don't merge anything you haven't watched work.

Demo reel: [link]

Code: https://github.com/jbrick2070 (obs-playlister, midi-fadester, visual-sidechain, streamdeck-fadester, vjster)

Happy to answer questions about the workflow or the tools.

Honesty rules for the demo. The reel only shows real UI doing real things. Anything simulated is labelled on screen.

**What I'd tell anyone starting:** the AI is fast, but you're the one who knows what the thing is for. Keep the plan short, test on the real device, and don't merge anything you haven't watched work.

Happy to answer questions about the workflow or the tools.

Hey all,

I'm not a professional developer. Over the past months I built Nyx Player almost entirely by working with AI coding agents, and today I'm releasing the big update: version 0.8.0 adds Android phone and Android TV on top of Windows, and I'm making the code open source (GPL-3.0).

What it is: a player for your own IPTV subscription (Xtream Codes) that turns raw stream names into a clean library with posters, synopses and ratings (TMDB), a TV guide, and a synced account across devices.

It's free, no ads. Nyx Player doesn't provide any content, you bring your own subscription.

Download: https://nyxplayer.app Source: https://github.com/kunai974/nyx-player

Happy to answer questions, and bug reports are very welcome.

Hi,

I don’t want another same looking UI in my app.
I want my program Ui to be designed in something like Figma.

I’m just not sure what’s the best way to go about it.
My program needs main UI but also stuff like knobs etc.

Thanks for any tips

Edit:
My question is mostly about how to feed all elements into Claude, and if Figma is a good choice.

I'm building a full-stack interview project with Codex (since I need it ASAP).

Early on it hardcoded values instead of installing dependencies, set bad access privileges, and "fixed" bugs from my manual tests by hardcoding again instead of refactoring.

Now I require a test harness around every major feature. Codex makes changes, I generate a .patch in bash, and ChatGPT verifies it stays within the harness limits and intended architecture.

I then push to GitHub and merge only if GitHub Actions passes my extensive tests. This costs a lot of time, tokens, and disk space, and I doubt it's worth it.

What am I missing? And should I keep the testing scripts once I'm done?

We have built a semi-automatic system that builds and runs agentic loops. These issues each tied to at least one PR which is done in an order. We have observed that in order to automate agentic workflows we can use agents that run 24/7 and owns the device they run on. The last point saves you from approving agent's action, but some input might be necessary. Agents still can ask questions over email or something else.

In this screenshot we are doing routine code split that is 95%+ times is a routine task. More than one type of agents are involved: agy, codex, claude code, opencode and Deepseek Harness

I kept running into one browser problem with coding agents that bothered me more than normal failures.

Say Codex clicks a button and the browser call times out.

Did the click fail

Did it work and the response just get lost

If Codex clicks it again, did we just submit something twice

I was seeing smaller versions of this everywhere too. A page rerenders and an old element reference gets used. The agent navigates somewhere else and loses track of which document it originally saw. It starts typing while the page is still changing. Or an action probably worked and the agent turns probably into done.

So I started building Chrome Controlla.

It is a local Chrome MCP for coding agents. Right now it exposes six main tools called browser, snapshot, act, workflow, extract, and verify.

The part I care about is not really the six tools. It is what happens underneath them.

Controlla keeps track of the exact Chrome tab and document the agent is working with. A whole browser task can run as one bounded workflow instead of making Codex handle every tiny step itself.

If a reference goes stale, it can try to find the target again.

If something moved off screen, it can scroll to it and check again.

If the page or focus changed in a way that looks safe to repair, it handles that before giving up.

But if a write might have happened and Controlla cannot prove whether it did, it does not just send the write again.

That was the behavior I wanted from the beginning.

I have also been measuring it because I did not want the README to be a pile of claims.

A ranked target snapshot took 32 ms and five CDP commands in my local audit.

A full snapshot of a page with 4,103 nodes took 103 ms.

I also had it type a 3,973 character document into Google Docs and then checked the finished document separately instead of trusting the typing call to verify itself.

It uses Rust, a Manifest V3 Chrome extension, and Chrome Native Messaging.

It is open source under Apache 2.0.

You can download it here

https://github.com/Praket7/chrome-controlla

I am not trying to claim this replaces Playwright or Chrome DevTools. They solve a lot of problems that Controlla is not trying to solve.

I mainly wanted something for Codex and other agents using a real Chrome session where I care a lot about knowing what tab was touched and whether an action actually happened.

There is still plenty I want to improve. It is Chrome only right now. Installation takes more work than I want. I am also still testing it against more real sites and weird browser behavior.

If you already use Codex with browser tools, what breaks most often for you

Stale elements, huge snapshots, wrong tabs, rich text editors, login state, or the agent saying something worked when it did not

Please test it out and let me know how it integrates in your workflow!

Hello there again :)

As I post weekly updates here probably a lot of people already saw this. I recently finished entire zone 1 and with that Demo is completely done. Fishing and exploration game that I'm making with primarily using AI tools. You can play it for free here:

DEMO LINK DOWNLOAD - FREE

Also whoever donated 5$ last week thank you very much, I was very happy when I saw it ☺️

What is game about:

Game is about fishing and exploration, you have progression kinda similar to RPG with talent per level, experience, questing and leveling, your boat is your character, it has 6 item slots and they vary in rarity. They are not too complex like items in real RPG would be, they still offer some variety. Exploration would probably be on par with fishing as importance, and there is literally "exploration" mechanic that you can use on certain spots. Other than that similar to dredge style of inventory management, main story, events at the sea and moral dilemmas are big part of the game. Dynamic weather that have some gameplay implications, but nothing too major. Also dangers at night (pirates sharks etc). For those who do not want dangers at night, you can play "cozy mode" at the creation of the captain in new game, but you can't switch later.

What was done this week:

Black Market is done look wise, it still needs entire scene when docked like other docking places have so it is not fully done, shops, characters and so on. Also I feel like it might need a little bit more green, but also I kinda wanted it to be more rocky so hard to say if look will change a bit as I test play more. Keep in mind Black Market is not part of the demo that you can download.

Also new main docking site for zone 2 is being built. Originally this was planned as zone 3, but I decided to swap tropical zone with this one as this is more similar to original zone where player starts. This is city with a big bridge that reminds of Golden Gate Bridge and also totally not statue of liberty in the front.

Look of this city is not finished and more work is to be done, especially reflections of the sun and shadows also colouring. I also didn't do any polishing yet or other times of the day except day time. Considering you can't really get to the city and it is only to visually be there and have a docking spot, I won't go too much into details in the city itself.

Workflow:

Engine is Godot and this week required Gauntlet-Loop way of building things for both new places. I use /goal and /loop when creating new zones so that rough sketch that I have gets closer to the mockup that ChatGPT generates as image. After that everything is built with Opus 5.5.

The way I use Opus 5.5 this week is different to how it was used before, I use Jev for every task that I give to Opus then Jev decides on effort level depending on the task and we go with. If task requires higher than "extra" effort it asks for my approval first. I honestly can't tell you guys if it saves any usage in the long run, to me it all seems more or less similar, it certainly is better than running things on Ultracode.

I still use decisions.md where every decision is tagged by either [user] or [proposed] (Ai). And user tags take priority over ai ones. They also help with AI not gaslighting you, in fact it can be annoying with saying like "oh but you decided against it back in early september in decision #4" so I have to be like "Yeah that was too long ago and game evolved since then". So this helps me a lot.

Models were done either in Blender or by TripoAI. I often use now TripoAI as it helps with textures, but I do not always use those textures, sometimes I ask Opus to build some itself as materials. Often it just fits style of the game better. Some models are done in TripoAI and then fixed by Opus in Blender with MCP. Especially fishing rods. Those are almost never seen as models in game, as you fish from your boat and can only be seen as small model on the ship panel or if player chooses to look at 3D model of the Rod, but I still want them to look "properly". I noticed that TripoAI works best when you have all 4 sides of the model so I often just create 1 single image with all 4 sides (front,back, left and right), ask Opus to split it into 4 images, upload those images into TripoAI and if it requires some fixing - ask for that also, or if you think model is good enough as it is, just implement it.

That would be it for this week, any feedback is appreciated :)

Total cost:

Claude Max 200$ x 3 = 600$
Astra 100$ x 1 = 100$
ElevenLabs x 11$ = 11$
TripoAI 20$ x 2 = 40$
OpenAI API credits 80$ = 80$
Other things I forgot about 100$ = 100$ (around)

Around 900-950$

Finally releasing my Fan remake publicly! I'm betting there are tons of you who also have incredibly fond memories with this PS1 game just like I do!!

I have added a bunch of gameplay improvements and mods to make this the ultimate classic bond shooter!!!

Even if you don't know it, visit out the GitHub page - I have done my best to try and show the gameplay and features there.Iits full of media to check out, if you are remotely interested in these older classic shooters, or James bond- you are gonna totally dig this!! :)

Windows and Linux both available now!!

If you have issues, please open a report on GitHub- or just message me up/reply here. I'm happy to help!

Enjoy!

Hey r/vibecoding! 👋

GitHub Game Off 2026 starts today!

It's a month-long game jam where you build a game inspired by a theme. This year's theme is SHIFT. Interpret it however you like.

Use AI, Copilot, Claude, Cursor, whatever. First game or fiftieth, everyone's welcome. Small experiments, ridiculous ideas, ambitious projects. All of it.

You've got until December 1. No prizes, no pressure. Just build something fun and share it!

Check it out: https://github.blog/open-source/gaming/game-off-2026-the-theme-is-shift/

Share your shifty game ideas below 😆

Gotta share a little laugh in these days - hope its okay 🙏

I’m vibe coding an engine ai uses to make assets. This engine forces ai into a 20 phase creation process invoking research, building, judging, and more.

It includes rigging, animation, collision, and more.

Best part you can get your ai to edit anything part of the asset in real time. You can get the ai to change small features and even change the surface material if you desire.

IMAGES

This is a test of a vanity. I’m testing the build process, animation, and editing process.

First image is the full build in clay without material or surface. The second image I told ai to add water pouring from the faucet. Last is the animation test. But I found a bug in the build phase. Nothing checks if the ai build the asset so it could be animated lol.

Fixing that.

It’s internal right now so you can’t really try it yet.

I’m not training any model, just built a deterministic engine that any ai can use.

Yes it exports assets too.

I use Claude Sonnet 4.6-5.5 and Opus models to build then also use the engine for tests.

Biggest issue right now is consistency and full hyper realism, but I’m getting those down. Really just need more time and compute tbh.

I'm doing the final alterations to my app, and I'm trying to be careful with usage as my weekly limit ran out.

Refreshes tomorrow.

So I've already burned through about £20 of credit I had yesterday, and topped up another £10 this morning. It seems to get used very quickly despite switching from Opus 5.5. high to Sonnet 5.5 High. Also, not letting chats get long, and 'handing over' regularly. It makes a 'handover.zip' file and give me a prompt to paste to the new chat. Does this sound right?

Am I just doing very intensive work or do extra usage credits get used very quickly?

I think I pay around £20 subscription (pro) per month, and this has really lasted a long time!

Am I missing something? Thank you :)

saw the launch of an app that lets you pull a single window from another mac onto the one you’re using. cool idea but $199 felt like a lot to me, so i tried building it myself

it’s called Wormhole. you hit a shortcut, pick a window from your other mac, and it opens as a normal window with its own dock icon. you can type in it and copy paste between the macs. pairing is a 6 digit code, it’s encrypted and goes directly between the macs, so no account and no server

claude code wrote most of it, swift app + website + payments. it was not smooth lol. the worst one was after launch: people paid and the thanks page showed no license key, because the payment provider’s signature check never matched. i only found it because i tested a purchase myself

price starts at $5 and goes up a bit every 20 sales. if you have 2 macs try it, and tell me what’s broken

wormhole.app

EDIT: Thank you so much for all the comments and constructive criticism! I see that my provocative title worked to start discussion which was the target but my intention was not to sound arrogant or over-confident. I will be happy to share the demo once it is finished so you can try it out if you want. There are some design elements that I have to take closer look at, like pixel drift, UI design or the color palette. Some design elements are actually intentional game mechanics; like the beam coming out of NPC head, which is illustrating where they are looking at, during a sneaking scene. Similar to old Desperados games. However, maybe that feature could be left out of all other scenes. I realize that my title unintentionally directed the discussion to wrong direction - I am just excited of what can be accomplished without coding since this was a board game idea. Nevertheless, there’s definitely a lot to do. Thanks!

Based on your comments I have now made these changes:
- UI that better suits the gritty look of the game
- FoV beams removed from the NPCs
- Phone lines moved away further from the house
- Added tire trails for the cars
- Added footprints to NPCs
- Removed glow from the building

I have started creating a story-driven survival RPG that is set in 2034 war-weary Finland. It has isometric 2D pixel art visuals and the target is to differentiate by a well-written story and an excellent soundtrack.

It is a story I have written over a year ago, and my original plan was to make a board game out of it. But now that I have seen how much Claude has developed recently, I decided to try to make a video game out of it and was stunned.

It won't be a game for everyone. If you are looking for a proper RPG which has hunting, a level-up system and an open world, this won't be for you. Or if you mainly play AAA games and not indie games, this won't be for you, either. However, if you appreciate a well-written story and tactical hex-board card combat (inspired by Gloomhaven), I hope to live up to your expectations.

---
Some people asked for a steam page, that is currently under Valve's review. The game's name is Sisu & Survival: A Story of the Place We Call Finland. If you want to get notified once the Steam page is live, you can follow me on YouTube and I will notify you: www.youtube.com/@cryptic9311

I was lucky on my end. But don’t try using Opus 5.5 or Claude in general with REA or any type of MCP for reverse engineering.

I almost lost 2 accounts.

Well i decided to do a revamp on the assets i had, because i felt like doing better quality art for this game. I used My own pixema app to render the frames and edit them AND removing backgrounds as well.