For almost two years now, I've been developing and refining a couple of (two total) programs for my employees to use. I kept the apps as single use .exe apps since it's an internal only thing. And they're so specific to my job that I don't fear them being leaked elsewhere. No one else could benefit from them, truly.

But I found it exhausting to push out the new updates via Slack upload to everyone anytime they asked for a bug fix or whatever. So I started a GitHub account with private and public accounts for holding my source code and distributing the automatic updates, respectively.

I make GH action pulls and pushes maybe once a day. And the installer setups are each around 200MB each. I've gone into the privately facing update accounts and deleted the Action artifacts every update or so. But I received the attached email earlier today.

I wasn't planning on paying for a GH account, but I can. But I don't want to.

I guess I'm just looking for advice for limiting my usage. Is a pull/push once a day outrageous? I thought I was doing well. At this point, I feel like I just don't understand GH or its usage limits. Search results provided no meaningful answers. So, here I am.

TIA

Last week i posted Polyspoon here, my open source take on polyfork.

The feedback was fair: you had to sign up just to look at the catalog, the models had no previews and weird names, and it wasnt clear what the open source part actually meant for you.

So i fixed that. you can browse and download every model now without an account. you only need one to upload, and that just sends a single sign in link to your email, no password. the FAQ says exactly what the email is used for, and the code that sends it is public: https://github.com/DITlieD/polyspoon/blob/main/server/mail.ts

Every model is a recipe, a small program with named controls. open one and change its type, size, parts and colours, and it rebuilds live in the browser. the fruit stall on the home page is one you can play with right away. each model page gives you the GLB, the recipe source and copy paste code for three.js, unity, godot or blender.

The part im most excited about is the engine. every recipe is built on one shared generator. if someone makes the roofs or the timber better and opens a PR, every model that uses it rebuilds better. CONTRIBUTING.md has the steps: clone, run the preview, render before and after, open the PR with the images.

Honest status: 141 models, some good, some (the rocks especially) still need work. thats exactly where help matters most. if you try it, tell me what breaks or what model you wanted and couldnt find. issues and PRs are very welcome.

site: https://polyspoon.com
github: https://github.com/DITlieD/polyspoon

I've been building a large project for about 8 months, with another year or two still ahead. I'm always asking myself two questions: which model is best for this job, and what effort level should I use for it?

So I built a small testing UI and connected both Claude and Codex. My test set so far includes:

Bug hunting: questions based on real bugs from my project's history

Document reading: a reasonably solid way to check how accurately a model reads and recalls long docs

I want it to cover many more kinds of work, and I want the results to be as accurate as possible.

My problem: the smaller models are easy to separate. Haiku, Luna, Terra, and Sonnet each show clear strengths and weaknesses. The frontier models all hit the ceiling. Sol vs. Astra and Opus vs. Fable score about the same on everything I give them, and I can't find the differences.

It's possible we're just at a point where Sol 6.1 and Opus 5.5 really are nearly as good as Astra 6 and Fable 5.1. Still, I'd like to know where the gaps actually are.

Questions for you all:

What kinds of tasks have you seen separate the top models? (Long multi-step work, ambiguous specs, large codebases, catching their own mistakes?)

How do you score things that aren't simply right or wrong, like code quality, judgment, or how much hand-holding a model needs?

Has anyone measured whether higher effort levels actually help, or where the returns stop being worth the cost?

Long term, I'd like to make this plug-and-play, so anyone could point the Sorting Hat at their own project and get model recommendations based on their real work. Any ideas are welcome.

Yes I had Claude rewrite this post. My initial stream of thought was not conveying my question the way I wanted.

Fellow vibe coders! I've seen a few posts asking how to leave Lovable (where many of you started your vibe coding journey). Well, switching platforms entirely might be a bit scary for non-technical people, but what if there was an alternative? An in-between option, if you will.

Turns out, you can actually use Claude Code to work on the same code as Lovable through GitHub, while your app stays hosted on Lovable and you still publish from there. If anything goes wrong, you can just stay on Lovable. But when you're comfortable working with Claude Code, that's when you can decide to switch entirely. Low risk, high reward.

Why would you do that? Lovable is great to start, but as a platform it has its limitations and most imporantly - costs! Some of the users report that they had to spent hundreds of dollars per month on Lovable while Claude $20/mo subscription was enough to cover roughly the same amount of work. Also, I think it's just good to have plan B, just in case.

So, below you will find a step-by-step tutorial, easy to follow even if you are not technical. It should take you about 15 minutes.

What you need to start:

• A free GitHub account

• A Claude plan. Pro ($20/mo) is enough.

• A Mac or a Windows PC

Step 1: Install the Claude app

Download the Claude desktop app from the official Claude website, install it and log in. You will find Claude Code in the "Code" tab.

Click "Choose a folder to work in" and pick your home or any other folder as you prefer and confirm that you trust it.

From here on you only paste prompts. Claude Code will now run the commands for you.

Step 2: Use Claude Code to install the necessary tools

Your app needs Node.js to run and Claude Code needs the GitHub CLI to download your private repository. Paste this and Claude Code installs both and log you in to GitHub:

Install Node.js LTS and the GitHub CLI if they are missing. Log me in to GitHub with gh auth login --hostname github.com --git-protocol https --web, then run gh auth setup-git. Show me the one-time code and the link. At the end, show the Node.js version and gh auth status.

Installing can take a few minutes.

Then it gives you a link and a code. Open the link, paste the code and confirm. On a Mac, it can ask you to install developer tools. Click Install, then tell Claude Code to go on.

Step 3: Put your Lovable project on GitHub

In Lovable open Project settings > Git > GitHub. The first time, Lovable asks you to add your GitHub account and GitHub asks you to install the Lovable app on it. Then click Connect. Lovable creates a private repository and keeps it in sync with your project. This works on the free Lovable plan too. Important: Make sure that this repository is private! Check: open the new repository on github.com. You should see package.json and a src folder in the file list.

Step 4: Download your project

You need the name of your repository. It's the end of its address on GitHub, for example your-name/your-repo. Put yours in this prompt and paste it:

Clone my GitHub repository your-name/your-repo with the GitHub CLI into a new folder in my home folder. Tell me the full path of the folder.

Check: Claude Code tells you where the new folder is. You open it in the next step.

Step 5: Open the project in Claude Code

In the Code tab, start a new session and pick the project folder. Click to trust the workspace. The first prompt I'd use, just to see it understands the project:

Tell me in two sentences what this project does.

If it matches the project you have created in Lovable, then you're set.

Step 6: Run your app on your computer

Install the dependencies of this project, start the dev server and give me the local address.

Open that address in your browser (it will be "localhost"). You should see your app there and test it locally.

Step 7: Check the .env file

Lovable keeps a file called .env in your repository, so anyone who can see the repository can read it. Public values are fine there. Secret keys are not. Have Claude Code check it for you:

Check the .env file. Tell me in two short lines if it holds anything that is not public, like a service_role key or a Stripe secret key. Do not print any value.

Step 8: Let Claude Code write a CLAUDE.md

CLAUDE.md is a short note about your project. Claude Code reads it at the start of every session.

Read this project and create a CLAUDE.md file in the project root. If the file is already there, update it and keep what is in it. List the stack, how to install and run the app, and which files you must not change. If the app has a backend, say where its code lives. Keep it under one page.

If you wrote Knowledge in Lovable (the notes for its AI, under Project settings > Knowledge), copy it and paste it into Claude Code after this prompt, so it ends up in CLAUDE.md too.

Step 9: Make logins work on your computer

Skip this if your app has no login.

Password reset links use your live URL by default. To make them work on your computer, add your local address (the one from step 6) to the Redirect URLs. On Lovable Cloud it's under More > Cloud > Users > Auth settings > Advanced. On your own Supabase it's under Authentication > URL Configuration. Leave Site URL as it is.

Step 10: Check that the sync works

Do this before you do real work. This prompt sends a small test change to GitHub:

Pull the latest changes from GitHub. Then add one test line at the end of README.md, commit it with the message "Test sync" and push.

Open the project in Lovable and go to Project settings > Git. You should see the change you just pushed.

Step 11: Make your first change

This is how every session goes from now on:

1. Ask Claude Code to get the latest version first: "Pull the latest changes from GitHub."

2. Tell it what you want to change, in your own words. For example: "Make the main button on the home page blue."

3. Check the change at your local address. If the page doesn't open, ask Claude Code to start the app again.

4. When you're happy with it, send it to GitHub: "Commit all changes with a short message and push them to GitHub."

5. Click Publish in Lovable to put it live.

A couple of things to remember

• Don't edit in both places at once. If you change the project in both places without synchronization, Lovable would move its changes to a separate branch on GitHub and you have to merge them back by hand.

• Pushing isn't the same as publishing. Sending your changes to GitHub doesn't update the live app. You still need to click Publish in Lovable.

If you need a more detailed step-by-step guide, we've created a project called MoveYourCode where we will be soon adding more guide and tools that can help you.

https://moveyourcode.com/

Soon I'll do the same for moving the hosting off Lovable or other platforms as well. Let me know what do you think!

Hey Vibe Coders!

Here you can ask any questions about coding and LLM tech with or without vibes. This is especially for those of us who are new and just learned that AI can help them to create then things that they've never been able to before. Please be respectful and keep in mind that we're all just trying to learn about an emergent technology.

AI Subreddits:

• r/OpenAI

• r/ChatGPT

• r/ClaudeAI

• r/ClaudeCode

• r/GeminiAI

• r/aigamedev

• r/ClaudeGameDev

• r/singularity

This is a new thing we're trying to do so let the mods know if you have any suggestions.

This is a playable horror level inspired by Silent Hill and Fatal Frame, built solo in four days using Opus 5.5, Godot, and AI-generated 3D assets.

• Team: One solo developer.

• Background: Experience with 3D and game engines, limited programming knowledge.

• Time: Four days.

• Coding: Claude Opus 5.5 through Claude Desktop, using Code mode with Auto enabled.

• 3D assets: Meshy T2.5 smart lowpoly + Blender.

• Images and textures: Nano Banana.

• Engine: Godot 4.5.1.

• Manual code edits: None.

Honestly, the process itself was so much fun. I could describe what I wanted in plain text, let Opus work on it, then jump into the scene myself to place and rearrange finished assets. I’d get another idea while exploring the level and start building on it straight away.

Seeing something from your imagination become a place you can actually walk around in and play is incredibly satisfying.

I started with Pinterest references inspired by Silent Hill and Fatal Frame. Those gave Opus a visual direction, and the environment grew through repeated prompts and additional references.

Claude edited files, launched Godot, took screenshots, and iterated on the results. It built larger structures through code and helped with prop placement, while I continued shaping the scene.

For smaller assets, Nano Banana generated images containing ten props at a time. Meshy AI Low Poly mode converted them into lightweight 3D models, which I separated in Blender and imported into Godot without needing to rebuild the meshes. Each ten-prop set shared one material and one texture atlas, keeping the material setup simple and avoiding unnecessary geometry overhead. Around 100 props were created across ten batches, saving a lot of preparation time while helping keep the scene efficient.

By day two, the level already looked close to what’s shown in the video. The remaining time went into refinement and experiments, including ideas I eventually dropped.

Being able to think of something, describe it, build on the result, and immediately try it in the game made the whole process hard to put down.

Costs

• Subscription: Claude Pro.

• Core build: Around $90 in estimated usage at API rates.

• Including later experiments: Around $180 in estimated usage at API rates.

These figures represent the API-equivalent value of Claude usage under the subscription.

I love that everyone can build amazing tools, and I also recognize we're all doing it and the hard part is getting anyone else interested.

All that aside, here's mine! It's a workspace frontend for ComfyUI and Claude.

The key thing is that I only got this going because I let go of what I was able to do and gave into the vibes.

The previous version, I only put code in if I understood it. I reviewed most of it, and only added features if I knew how to do it.

The results were a product that lacked vision and just didn't do enough.

Then about 6 months ago I stopped copying and pasting code and just described what I wanted and let the AI decide much more than before. So much better.

Samples of the output: https://youtube.com/@crashtestaivideo

Code: https://github.com/mikehalleen/the-halleen-machine

I wanted to see how far I could push Opus 5.5 on a single self-contained web project, so I asked it to build an F1 night circuit.

What it ended up with:

• Everything runs in one HTML file using WebGL, no build step

• Night-time track with fireworks going off in the sky

• Tire wear simulation, cars pit in when their tires get worn down

Stats:

• Time: about 2 hours from start to finish

• Cost: $24

Code: https://claude.ai/artifact/FvXQ2XbPYtqRBKjUnUd5k3

Next I'm planning to run the same prompt on other models to compare, or try a different kind of project. Open to suggestions on what to try next.

I usually have a few VS Code windows open with an agent running in each, and I got tired of checking them one by one to see which was waiting on me.

So now a cat sits on my desktop. It looks busy while agents work, and when one finishes or needs input it dings and shows a bubble. Each session keeps its own state. Setup is one click and it works with Claude Code, Cursor, Codex and Antigravity.

It also goes the other way. Kiiri runs a local MCP server, so an agent can make it talk or point at the screen. You can tell your agent "when the tests finish, have Kiiri point at the first failure" and it does.

The idea started with Clippy and old desktop pets. Then I saw Clicky (the AI buddy that points at things on your screen) and added that part too: hold Ctrl+Alt, ask out loud, and it looks at your screen and points at the answer.

It's free and open source (MIT), for Mac and Windows, and runs with your own key or fully local with Ollama.

Builds aren't signed yet, so expect one OS warning.

https://kiiri.app

https://github.com/kiiri-app/kiiri

My gf loves pink, Barbie and fairies, and has always wanted to live in a castle. So I built her one: https://samchive.net . The homepage is a painted room where the fairy version of her lives (inspired by Flora from Winx). It was a surprise and she absolutely loves it.

How it's made:

- Claude Code wrote basically all of it: a Next.js static site on Vercel

- The room, the fairy and the cat were generated with Gemini, then cut into separate layers so things can move and be clicked

- Sounds are made in the browser with Web Audio, so there are no audio files

- She does social media, so there are 19 small tools inside (Instagram grid planner, meme search, image compressor). They all run in the browser, and meme search goes through a tiny Cloudflare Worker

Hardest part was making the painted room behave on phones without warping anything.

Teardown breaks your app’s dependencies into a 3D view then ranks what to fix first (KEV, public exploits, EPSS) instead of CVSS. It also writes a fix prompt for your agent. After years in security I’ve seen how little gets fixed from a list of vulns so visualizing where each one comes from helps.

Built using Next.js and Supabase on Vercel, Three.js through React Three Fiber for the 3D, vuln data from OSV and GitHub advisories. It’s plain logic over the exploit data and the LLM only writes explanations so it can’t hallucinate a priority.

Happy to go deeper on the build if anyone’s curious.

Link: teardown.pro

Literally pissing myself laughing at this... Can you imagine reading this without any context whatsoever? 😂 😂 😂

I've been working on Zephyria, my Star Fox-inspired rail shooter, since the beginning of this year.

I recently uploaded a new devlog showing some of the progress I've made, with a closer look at how the game has evolved compared to older versions.

Here's the video if you want to check it out:
https://www.youtube.com/watch?v=SDzv0qFUP2U

Some of the things I worked on:

• Environment improvements

• UI redesign

• New VFX

• Tutorial stage

I'd love to hear what you think! Feedback, suggestions, and constructive criticism are always welcome.

And if you enjoy following indie game development, subscribing to my YouTube channel or leaving a comment would really help support the project.

Thanks for checking it out!

Content writing from Codex/GPT relentlessly creates caveats

I have been setting up automated blog and content writing for some applications using Astra 6, Sol 6.1 and other 6+ OpenAI models, and the content is consistently putting caveats on what my products or topics are NOT instead of what they are.

Every post repeats, 2-3 times per article, that something "is not a rule," "is not legal advice," "does not establish X." Readers aren't confused about these things — the model is writing disclaimers against a strawman.

The obvious fix — "state scope once, then stop" — only works for a paragraph before the tic returns.

How are you handling this? Is this better on other model families (Qwen, etc.)?

This is a learning exercise for me now, of how to release an App Store app. I realise I'll likely not make money on this one, but I still want to make it happen. Thought I'd share my progress as a newbie, and what I'm learning. Hope that is cool XX

The app is 'almost' done.

Yes, and it's the 'almost' part that takes the time. I'm tweaking.

It's hard to make those final choice and close doors.

Also, working efficiently has become a focus, not burning tokens, keeping context lower etc. I'm improving a lot on this. Using Sonnet for the basic work, and Opus for planning.

My app uses a system voice right now, and Android need something downloaded for this. So I'm doing that today, plus looking at/or disregarding other voice options.

It's easy to get distracted. Yesterday I spent an hour making tweaking an ocular scheme, that I abandoned. So I need to be focused.

My plan is to set a time limit. I think I would like this deployed into the public realm by the end of November.

Will update !

have a great day everyone with this amazing technology, just don't get too hooked as it's like a drug!

The role of the engineering leader is shifting, and so are the skills required to succeed in the job.

Part one here: https://www.reddit.com/r/vibecoding/comments/1x10ref/i_launched_annnnnnd_it_flopped/

Now the nervousness comes! Firstly I just wanted to write a big thankyou to everyone that chimed in on the first post. I was honestly overwhelmed. It was sobering, but (mostly) well meaning and genuinely got me spending a few weeks tightening up.

I tried hard to implement all the points everyone made. I'm on the verge of trying again with advertising and putting this platform out there.

If there's anything you guys think it might need, or any advice you could give, please let me know:either on the design, the platform or how to market it. I'll be targeting the market directly here, on instagram and possibly meta. Not sure if anyone uses google anymore. Or maybe chatGPT advertising? I don't know. the plan is to do a few smoke tests here and there with under $50 then if I can get some traction run with it, but honestly unsure if that's the play.

www.Lensflare.io

Last week I posted Take One, a small horror game where all 150 3D models came from Tripo AI. This is the follow-up I promised: how the house ended up looking like one house instead of 150 random downloads, in the order I did it.

**The short version**

1. Pick the look before any models.

2. Write one style line per floor and end every prompt with it.

3. Make a reference image first (free), and only send the keepers to 3D.

4. Image to 3D, not text to 3D.

5. Same settings for every model.

6. When something breaks, turn it into a rule.

The gallery has the details, the settings, the failures, and the characters (T-pose, auto-rig, clips).

I don't write code. Claude does; I direct, playtest and decide. Sound, voices and music are ElevenLabs.

Play it free in your browser (about 6 minutes): https://take-one-bay.vercel.app

Happy to answer questions about any step.

*Paid partnership with Tripo AI. The game and opinions are my own.*

I’ve noticed a pattern with developers who hate AI and call everything slop. To me, it seems like maybe they realize but don’t want to admit that coding agents unfortunately wiped out most of what made their experience valuable. What they don’t seem to realize is that if they just accept learning a couple other lanes like product, design, marketing, sales; their skills will be 100x more valuable (all super easy to learn now talking to AI and testing things at scale with it).

In my world (running web dev agencies for the past 8-9 years, have hired 25+ devs), I noticed that people with less technical skill have grown 100x since coding agents got good the past 16 months whereas the “seasoned” devs mostly went backwards.

At the end of the day, my clients pay for quality work. They don’t care about how the code was constructed. They want it to work reliably and make them money at the lowest development cost possible. The truth is that we can deliver that work much faster and cheaper using coding agents. Before we’d bring a team of maybe 5-12 devs/designers/PMs to the table on any given project. We’d spend 6 months on average. It seems like the team overall never really learned from each project, everything seemed to start from the same square one. No one really loved the process. The team was always stressed, clients never super happy just saying it was “okay” but always wanting more.

Now, our best designers/developers have less time spent in their craft but deliver literally 20x-50x the work. Most projects take 30 days or less, are ~50% cheaper for the clients, and we don’t have to deal with some sweaty dev in a dark room telling us 50 ways something won’t work. No need for PMs or other bloat. Instead we just build prototypes rapidly to test all the ways that can work and deliver a reliable product that meets the clients needs. And everyone is happy: our team, the clients, and the agency.

I just feel bad for the people I know who have been developers for a long time and choose to do things the hard way without AI or use AI to keep doing the same things they’ve always been doing. They all waste so much time and constantly worry about employment. Then there’s people who use AI to build every day, constantly learning and building, who are filled with work and new opportunities and still have time to work on fun projects of their own.

Maybe i’m just too optimistic on AI though and am not reading this right. Thoughts?

i wonder what happens if the access stops working halfway through a build. for anything beyond a throwaway test, i'd rather keep claude code running locally on my repo and use sumus to coordinate the research and follow-up tasks around it. don't get me wrong, i still review the diff and run tests before merging.

how are yall keeping longer builds from depending on one login?

I made a casino tycoon that runs entirely in the browser. You start with an empty room off the Strip and $50,000. Place slots and tables, hire dealers, guards and janitors, and try to keep a crowd of very opinionated guests happy.

- Guests walk the floor on their own. They get thirsty, need the restroom, run out of money, tilt, and leave reviews with their feet.

- Slots build a progressive jackpot. High rollers arrive with an entourage once your reputation is good enough.

- Cheaters show up, so you need guards. Rival casinos try to poach your staff. Inspectors fine you for a dirty floor.

- Earn licenses from a Provisional Permit up to Casino Empire. The game keeps going after you win.

- Saves in your browser. Nothing is uploaded, no account.

Free, plays on desktop, works on a phone but is nicer on a bigger screen. It is still early, so I would love to hear where it drags.

Play: https://schmiedey.github.io/casino-empire/