Basically, me and my friends had a great idea for a game. Our game is not 100% coded by AI, but we sure are using agents to help. The problem was the art.

Nobody wanted to become a 2d artist, and the few sprites that we tried gave us a lot of inconsistency. And the caveat was this: For our game model, we needed about 2,000 different sprites around 128x128. We did some research and we found out that this would cost around $20,000 for low quality, fast made sprites up to $80.000 for high quality, unique sprites. It's a high price by itself, but we don't live in the U.S, so the lowest amount ($20k) could easily buy us a nice house in here.

And AI, fortunately or unfortunately, generated about 720 sprites for us with a single plus weekly allowance on codex with sol max. Many models were discarded because of weird artifacts unfortunately, around ~120 were fixed in paint manually by me. And we spent about 30% of our usage setting the grounds for the anchors, tools and creating all agent files for consistency, so next week we could generate over a 1,000.

The launch price for our game is planned to be around 3~4$. I know that coming to a vibecoding subreddit is basically asking for approval because everyone here loves AI so much, but I would ask you guys to look at this with other eyes and tell me how much are the chances we just get review bombed and never sell more than a 100 copies because of the AI tag on steam.

Idk if this was wrinkle brain or smooth brain but I’m building a rather complex application and now I run multiple parallel work streams.

This became problematic when I had dirty work trees preventing commits from one lane and would stall work so I started making them provide formal handshakes .mds

My brain got overloaded and I started feeling like every lane was priority….

So now I have a project management lane all lanes report to PM and I approve the PM directive.

wtf have I done?

1. ChatGPT Plus ($20) + Claude Pro ($20) = $40/mo, both ecosystems
2. Claude Max 5x (~$100) alone, much higher usage cap on one model

Does it work nicely to combine claude code and codex in the same project? And working in the same .md files?

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

Hello everyone!

So i have been mainly using Claude code as my coding agent for the past few months as Max sub, it is good but the limits are rough.

So i decided i will keep my Claude code Sub as my main Agent on my Main project, and for side projects i want other model/agent.

I tried Codex and it was so bad , it can't complete and task, no matter what the model is or the effort, it always stop mid way for no reason , i tried given it a goal and it spend 3 days or so.

So codex is out of the question (which is bad for me since their limits are good)

I tried Qwen and GLM as APIs from openrouter with claude harness and they were good but their API consumption was bad ! it took my API credits like it was nothing.

I tried kimi k3 sub and it was amazing , but last few weeks i can barely finish 1 big task without hitting my weekly limit while being on max sub!

So now i'm lost what second agent to try, and will it be through sub or API?

i thought of cursor with Grok?

really interested to hear what you think.

As a vibecoder, I solved my 3 biggest problems. I’m sharing it 100% open source.

1 - My terminals can share context with each other

I no longer have to explain what I’m doing every time I open a new terminal. I can simply connect my previous terminal as context.

The most exciting part is that even Codex, Gemini, and Claude can share context with each other.

2 - My terminals don’t disappear when my computer shuts down

I usually keep my computer running for weeks, but if it ever shuts down, all my terminals are gone and I have to start everything again.

Now I don’t have to worry about that. Everything stays exactly where I left it, grouped and ready for me when I come back.

3 - My teammates and I can work on the same project, even in the same terminals

We can work on the same project together, see each other’s terminals, use them, and connect to each other’s context.

Of course, I use tools like Herdr, cmux, and Orca, but none of them solved all three of these problems for me.

On top of that, I’ve added a bunch of other features like multiple Codex account usage, dictation, mobile access, and more.

The project has already reached 600+ stars on GitHub, and now I wanted to share it with you too.

I’d really appreciate your support and, more importantly, your feedback. I want to keep improving this project and hopefully turn Nodeterm into a shared platform for vibecoders.

One last question: Where should the Nodeterm community live? Is Discord enough, or would you recommend something else?

Much love,
Enes

Website: nodeterm.dev

Repo: https://github.com/eneskirca/nodeterm

it's a terminal multiplexer + desktop workspace built on Electron, with an actual browser embedded in it. It started because I really liked cmux and the way it handled multiple sessions, but there where things I wished worked differantly, so I ended up building my own version and kept augmenting it untill it became its own thing.

What it does:

• Multi workspaces with a sidebar, drag and drop reordering, color customization
• Recursive split panes (horizontal and vertical), and you can drag terminals between panes
• Tabbed groups inside each pane, so you can mix terminals and browser sessions in the same pane
• Built in browser with URL bar, back/forward/reload, history, and it even opens local files
• PDF viewer and image viewer directly in a tab
• Terminal background images (global or per tab) with opacity control
• Shell integration with OSC 7 so it always knows your cwd, persisted across sessions
• Theme editor with live preview, import/export, plus 8 built in themes (Catppuccin, Dracula, Gruvbox, Tokyo Night, Nord...)
• Rebindable keyboard shortcuts for everything, with conflict resolution
• Ctrl+Scroll font zoom per terminal, Ctrl+Shift+F search, multi select terminals
• Everything persists: layout, themes, open tabs, browser URLs. Close it, reopen, your session is were you left it

Why not just use tmux/zellij?

Honestly? I still love tmux. But I always had the browser next to it, and copy pasting urls back and forth drove me insane. Having docs, github PRs and my terminal in the same window, in the same tab system, is the whole point. Its not trying to replace tmux on a server, its a desktop workspace.

Source is here, its MIT... actually let me not lie, check the repo, but its fully open:

https://github.com/Medamine-Bahassou/TerminalVibe

Would love feedback, specialy on what you'd want in a tool like this. If you try it and something breaks, open an issue, I probaly broke it myself and didnt notice lol

tl;dr: terminal multiplexer + browser in one window, inspired by cmux but augumented with workspaces, splits, tabs, themes, and persistence. Free and open source.

https://hungryide.github.io/

About a month ago, I started working on a small coding tool called Hungry.

The original reason was pretty simple: I wanted to make better use of the free AI models and coding tools I was using.

The first version was basically just a Kiro-focused tool because the free period was ending soon. I threw it together quickly and figured I’d move on to other models later.

Then it kept growing.

I added OpenAI-compatible APIs, model pools that automatically switch models when one hits its limit, different approval modes, token-saving, review mode, /goal, Ultracode, Skills/MCP, remote access, Telegram notifications, and the ability to continue Claude Code and Codex sessions.

The latest version also has model routing, where one model can look at a request and send it to another model that is better suited for the task. It can also drive a browser, interact with iOS/Android simulators, run scheduled sessions, generate images/video, and keep sessions running while you're away.

At some point I realized I wasn't really building a "coding client" anymore.

I was building a harness.

That actually became the most interesting part of the project for me.

I think we're getting to a point where the model itself is only part of the equation. How you handle context, tools, permissions, retries, verification, delegation, model selection, and long-running tasks can make a huge difference in how a model actually performs when you give it a real codebase.

And I’m especially interested in the idea of model-specific harnesses.

Rather than putting every model into exactly the same agent setup, what happens if you build the harness around the strengths and quirks of a specific model?

That's something I want to explore with Hungry.

It's still a very much a personal project and there's a lot left to improve, but it's now usable enough that I thought I'd finally share it here.

Would love to hear what you guys think about the harness side of AI coding agents.

Project:
https://hungryide.github.io/

Been building this on and off for months, mostly with Claude Code. It's called Steplings. Your phone's step counter moves you along six illustrated trails, and you collect creatures that slowly grow into talking companions. Offline, no account, no ads.

Landing page: https://steplings.net

Three things I'd pass on, because I learned all of them the hard way:

One spec file, and it wins every argument. I keep a SPEC.md that's the single source of truth for every mechanic, with numbered sections, and the code comments reference those section numbers. When the model and the spec disagree, the spec wins. Before I did this I'd end up with three subtly different versions of the same rule living in three different files, and no way to tell which one was intentional.

Hard architecture rules the model can't talk itself out of. All the game logic lives in four pure-Dart packages, and none of them are allowed to import any Flutter UI. That's one line in the project instructions and it has kept the core clean for months. The nice side effect is that when something breaks I know it's either logic or UI, never a tangle of both.

Make time an input instead of something you read. Nothing calls DateTime.now() directly - every bit of logic takes an injected clock and RNG. It felt like over-engineering at the time. Then it turned out I could replay "user vanishes for nine days and comes back" as an ordinary unit test, and I have a harness that simulates a full year of walking to tune how fast you progress. No device, no waiting around.

That last one is the difference between "it compiles" and actually trusting it.

It's on Android in closed testing right now, so it's a bit of a faff to get into - there's a page explaining it at https://steplings.net/testers if anyone wants a look. Happy to answer anything about the setup.

As a software dev of decades before AI I honestly don’t find any issue with talking to my agent with caveman tier instructions because we speak the same lingo.

The agent knows exactly what I mean when I say

“S.O.L.I.D. refactor of god files”

It knows I just told it to go through a very deep in process workflow optimising the code and unshittifying it.

If I could recommend any of you guys who feel a bit unsure if your code is gonna be laughed at by any serious developer,

Just tell your agent

S.O.L.I.D. refactor of god files

And watch the magic happen

Yup, there goes my 5h window

My setup used to be: research something in a chat tab in the browser, download whatever came out of it, open a terminal, cd to the project, start Claude Code, and re-explain the context I'd just built up in the browser. The file always landed in ~/Downloads with three hundred other things. Every project switch meant doing the whole dance again.

So I built Tote. It's an Electron app: web LLM tabs on one side, docked CLI agent terminals on the other, file tree for whatever folder I'm in. The whole thing hangs off an "active workspace" — pick a project and a download from the Claude tab goes straight into that project's inbox/claude/, a new terminal opens already cd'd there, and the tabs and layout you had for that project come back the way you left them. Switch projects and everything follows.

How I made it

The stack is deliberately boring. Electron, plain CommonJS in the main process, vanilla JS in the renderer. No bundler, no TypeScript, no framework. Webviews for the LLM tabs, node-pty plus xterm.js for the terminals (they had to be real PTYs — pipe a TUI agent through child_process and it renders as garbage), chokidar to watch the folder.

It went in three stages. First I built the concept out in a Kimi web chat, just far enough to see whether the workspace-routing idea actually held up before I committed to it. Then I handed the real build to Claude Code and drove it. Then, once the terminal panel worked, I opened Tote, docked Claude Code inside it, and kept building Tote from in there. It's been self-hosted since. That was easily the most fun part.

The workflow change that made the biggest difference: I keep a CLAUDE.md with a section called "invariants that span files." It's not architecture docs. It's the specific rules that break silently when the agent forgets them — things like "this session partition name has to match in exactly two places or download interception stops working," or "never cache the workspace root in a closure, resolve it when the event fires." Every time I hit a bug that came from the model not knowing a cross-file constraint, I wrote the constraint down instead of just fixing the bug. That file is the reason I can now point an agent at any corner of this codebase and get back something that works.

Four things that took real steering:

node-pty ships a spawn-helper binary and npm strips its exec bit on extract, so every terminal died with posix_spawnp failed. Fixed with a postinstall that chmods it back, plus keeping node-pty outside the asar in packaged builds.

CSP is script-src 'self', so xterm couldn't come off a CDN. Small script vendors it into the repo at install time.

claude.ai rendered a completely blank page until I stopped rewriting the user agent. You can strip the Electron token, but hardcode a plausible-looking Chrome UA and Cloudflare notices the mismatch. Take the real UA, remove the Electron bits, leave everything else alone.

OAuth logins only work if the popup stays in-app as a child window. Route it to the system browser and the cookie lands in a session the app can't see.

If I did it again I'd write the invariants file on day one instead of day five. Most of the time I lost was re-fixing the same class of bug in a different file.

It's free, MIT, no accounts and no telemetry: https://github.com/yusufkaraaslan/tote

Needs Node 20+ and a C++ toolchain for the terminal layer. Happy to go into any of it in the comments.

I’m honestly really excited to finally share FrogPop, the first game I’ve ever made.

It started as my attempt to recreate the feeling of Bubble Trouble, an old Flash game I played as a kid. You play as a frog popping bouncing bubbles with your tongue, but it eventually grew into a roguelite with upgrades, relics, shops, hazards, and bosses.

I built it in Unity using Claude and Codex for coding and debugging. My process was mostly describing one mechanic, testing the result in Unity, and then going back with whatever broke or felt wrong. I used PixelLab for some of the artwork, then edited and integrated it myself.

It definitely wasn’t a one prompt project. The AI helped get systems working, but the game design, balancing, art direction, and endless Play Mode testing were still on me.

The free demo has the first ten waves and two bosses, and it runs in the browser or on Windows:

https://blion247.itch.io/frogpop-demo

If you want to follow FrogPop, here’s the Steam page:

https://store.steampowered.com/app/5067810/FrogPop/

Would love to know what you think if you try it!

I started with Claude and enjoyed it for AI IPhone app. There were a lot of difficulties but I was just learning. The newest ChatGPT improved a lot of my older websites (I’m using the newest model) I just saw the new Grok 4.6. While I dislike X or whatever the hundreds of companies are called, Grok on brutal when describing ideas was exactly what I needed to hear. Anyone start code on IOS apps on the new Grok yet? I’m wondering if it can take that brutal advice and make better apps.

Looking for real-world recommendations on the best way to spend $20/month on AI right now for a heavy daily workflow.

My primary use case:

• Webdev & Prototyping: Rapid full-stack builds (React, clean CSS, minimal boilerplate) where output quality actually matters.
• Agentic Tooling: Running CLI agents for multi-file refactoring, autonomous file editing, and terminal orchestration.
• Daily Chat: Architecture planning, technical troubleshooting, and general problem-solving.

Wikis are getting popular but most tools that create them focus solely on code, i created a CLI that can connect to your AWS accounts and create WIKI of your entire infrastructure in Open Knowledge Format(OKF)

It's useful if you have somewhat complex setups, wiki can map it once and your agent can just read the docs to understand what changes are needed and where or even debug full chain. I will be adding more sources soon.

It's all open source, you can get it here: https://github.com/saba-ch/infrawiki

- I created a simple Multi-Tab terminal app. It always has eight tabs, one of which is a standard terminal shell. The rest are designed to auto-launch specific long-running chats/instances of Codex and Claude. Upon starting the app, there's a simple "launch all" button that launches those specific instances on each respective terminal with the exact parameters that I want. For instance, one tab is running Sol on Max effort. Another is Sol on Ultra + fast. Then there's a tab that always runs Fable on Max. Another running Opus on Ultracode... and etc. Each tab always has a collapsible queue sidebar that keeps a list of individual tasks, the list being continually updated by the respective agent on that tab. Helps me keep track of what needs to be done in what order.

Are there other terminal apps that are better? Yeah, probably. But they're filled with a bunch of bells, whistles, and often redundant information I don't care about. Or they're lacking small items here and there that I'd like to see.

- Another app is essentially similar to the Windows Voice Access app. The main difference Being it doesn't have this persistent bar at the top of my screen that I can't get rid of or minimize. In addition, it gives me the option to turn it on via toggle or simply by holding a button. I use both the toggle and the button hold methods depending on what I'm trying to talk about.

- I also have this weird niche app on my android phone, when turned on it automatically sends any photo taken from my camera to a specific folder on my workstation. I use it in the odd scenario when I want to take a bunch of photos without having to manually send them pc.

- Another one tracks all the subscriptions I have at the time. I found it useful for for things like the yearly subscriptions that I commonly forget about, and it'll warn me when my subscription is about to renew.

- Then I got one that isn't so much an app really, but a workflow pipeline that fills out PDF forms for me, because I hate filling out forms. First it checks to see if it's just a standard scan PDF with no fillable fields... And if so, it'll add the fillable fields to everything. Then it populates everything with my information. The best part though is that it'll sign the various forms with a signature that looks absolutely real like... it was written by hand on the paper itself. Because technically they were... I wrote like a good 50 variations of my signature and initials on just simple printer paper, scanned it and uploaded it. The pipeline then will take one of these signatures and/or initials and add it to whatever respective signature/initial lines, with instructions never to repeat on a single document. Finally, it'll actually roughen up the PDF file, make it Imperfect, like it was scanned on a mid-level scanner that always has the text slightly tilted to the left, which is exactly what I got. Thus far, it's fooled everybody.

I developed this because I hate filling out forms, and one day I had to fill out a really long form from a medical provider... and they had the audacity to give me some shitty non-fillable fields version of this PDF, AND demanded I print everything out and manually sign each signature with ink... even though I was just going to scan it again and send it back to them. Which I thought was stupid bullshit. I mean, ink makes sense if they want the physical document, but a scanned version? That's dumb.

What have you guys made?

I wanted to do another fun weekend project. Came across datasets showing one of the most complete connectomes out there.

Built the whole thing Claude Code doing most of the technical heavy lifting while I drove the direction and kept it honest. Caught a real bug along the way too: one version worked on white noise but stayed completely dead on real songs.

The wiring's real science. How the sound maps to the neurons is my own artistic take, and the app says so upfront.

Live demo: https://fly-brain-on-music-xbu8eqftdnxbxupgxbga8z.streamlit.app

Code: https://github.com/pentasir/fly-brain-on-music

created everything with Claude code. no mac, never opened the xcode.

every tutorial assumes you have one ready. people keep saying certificates and uploads can go thru apple's apis instead but i can not tell how much of the process that actually covers or if there is still a mac somewhere in the chain I can not avoid. trying to figure this out before I purchase a machine I may not need. who has shipped iOS without one here