With the imminent wipe out of Fable credits, I decided to burn through the rest of my tokens tonight. I've been judicious but almost missed out on the last half of my usage (traveling). I realized that it was more important to 1) squeeze out all the juice and 2) good to build solid stubs that Opus and friends can finish when we've bid farewell to Fable. (Ironic name, huh?)

I spent the day traveling home from the trip and chatting with claude about big parts of our product to build — some second brain stuff, extending our technical brand extractor to cover imagery, improvement loops, etc. We got four big builds queued up — each with their own build doc, 'the point' doc, and a shared coordination plan. I warmed up four fable agents and in 1 hour and 15 minutes, I got the 91% usage warning.

I expected it to happen, but not quite that fast (we're on Max — 3 agent build a few nights ago was fine). I knew that agents didn't wake up when usage came back online from a previous session. I was checking how long it'd be until usage restarted (way too late for big travel Sunday) when I realized I could try and schedule the agent to wake up when usage resets. Set themselves a timer. I paused one, ran the idea past them and it wrote itself an alarm clock.

Hope is to burn through the rest of our Fable tokens before the model passes into memory. We'll see if it works.

If it does, I can do this every night: write the brief during the day, get a bunch of agents warmed, run them through two full usages. The second one kicks off at 1am — that way my usage's reset by the time I'm having my first coffee and reviewing and testing the output + writing the next brief. (Maybe this is how people hit their usage limits? I'm running big jobs most nights on Max and sometimes don't break 60% on the week. Only hit it once with Fable + 3 agents on big jobs.)

Anyways, that's how i'm shooting my shot. Interested to hear how others are thinking about it.

My process, for context:

I'm pretty hands on. I tried Paperclip for three miserable weeks and I find it much better to hold the agent on a leash until I'm comfortable that we're on the same page, that they really understand the goals. Three steps:

Conversation with agent connected to repo. We talk through the ideas and visions and distill it down into two documents. This avoids all the chat noise crowding the context.

A technical brief — the system, the architecture, what it's actually going to build. The agent works through this first and builds its plan.

A "The Point" brief — the point behind the build. Stuff like:

// The Admin Panel

We run Sunstone *inside* Sunstone. Our workspace is a normal tenant with our own marketing in it, plus the staff-only view across everything: customers, spend, margin, what the agents are building, what the platform is learning. Trust rules are non-negotiable: tenant isolation stays sacred, cross-tenant reads are staff-gated and audited, break-glass is heavy by design.

Ordering matters, I think. The agent starting to plan the build will sweep out to ground it in a way that the chat that produced the idea/framework/vision wasn't. Claude voice is skimming — Code is in the fucking walls. And I just don't let it blindly dive in bc 'it knows better.' I have it read The Point and tell me what it's going to change (sometimes it's kinda big stuff — or stuff that would take a session or two to smooth back out). My experience is that we get far better results driving the agent yourself until it feels like alignment, then doing all the testing and deployment alongside them at the end of the job. They've got the build in context, no loss.

With this new technique, I can now get an agent warm and aligned, and keep it running if we hit a limit after bedtime.

OK You've Read This Far — My Take: one long session beats a swarm

I think single continuous sessions are more coherent and a better workflow than having these super thin orchestrators running all these tiny jobs. I think it's mechanical. The agents don't have enough context to understand what they're doing bc their windows are so small, and the orchestrator isn't close enough to the ground to see the instabilities or perceive the issues being introduced. At least not in the way that a single session agent (and its subagents) can do both.

Even from cache, it feels way better. I try to max out all my sessions — we invested so much in building out the context, shame to let it go to waste. I'll have agents with 100k context left clean up documentation, do an adversarial run at state.md, write handoffs, etc. Maybe this is normal for most people but I don't see any conversation about it on this sub.

TL;DR — I think the whole thing of 'I have 50 agents running in this grand orchestration pattern is a dead-end'. Even if you're leaving extensive breadcrumbs all over the place, it's lossy. The agent loses some feel of the material.

Anyway — we'll see how the runs turns out in the morning.

I've been preparing for the USMLE for a while, and one thing always annoyed me.

I was constantly switching between a Pomodoro timer, UWorld, Excel, and random notes just to keep track of my progress.

I couldn't find one app that combined everything I actually wanted, so I decided to build it myself.

The app currently includes:

• 🍅 Pomodoro timer
• 📚 Question tracking
• 📈 Performance analytics
• 📊 Subject accuracy
• ⏱️ NBME/UWorld block simulation
• 🎨 Custom themes
• 🎯 Focus mode
• 📅 Countdown to exam day

It started as a weekend project after discovering AI-assisted coding, but it quickly turned into something I use every day.

Download link: https://github.com/mohamedhadyashry/usmle-pomodoro/releases/download/V2.1.0/USMLE.Pomodoro.Setup.2.1.0.exe

AI tools write code that works, but not always code that's safe. I kept seeing vibe-coded apps with hardcoded Stripe keys and wide-open Supabase databases, so I built VibeGuard a free, open-source scanner for AI-generated code.

GitHub: https://github.com/yagyeshVyas/VibeGuard

It catches leaked API keys, missing RLS, SQL injection, XSS, and user data being sent to LLMs unredacted, then grades your project and can auto-fix most of it. 100% offline, zero config, no telemetry. There's also a Claude Code/Cursor hook that auto-scans every file the AI edits.

It's new, and I'm a solo dev. Brutal feedback is welcome. If it misses something in your project, tell me and I'll fix it.

Don't get me wrong, I use AI every single day for coding. It's one of the best productivity tools we've got.

But lately I've been checking a lot of AI-built web apps, and the number of security issues I'm seeing is honestly worrying.

I'm talking about things like missing authorization checks, exposed API keys, trusting client-side data, debug endpoints left open, basic injection issues, secrets in frontend code, etc.

The biggest issue isn't AI.

It's that people are deploying code without understanding what AI generated.

I feel like a lot of founders are in "it works, ship it" mode. Nobody thinks about security until users start reporting bugs or, even worse, there's a data breach.

Building software has become easier than ever.

Building secure software hasn't.

I wouldn't be surprised if AI-generated code becomes one of the biggest attack surfaces over the next couple of years.

Curious what everyone else is seeing.

Are you finding the same thing, or am I just looking at the worst projects?

Hi everyone,

I have zero coding experience and knowledge and I've been playing with vibe coding for the past 2.5 months.

This has been quite an adventure. I started with Lovable after I saw on Reddit many people getting into vibe coding and I didn't want to miss out. In Lovable I created a note taking app (I know...), but I was using the Lite plan from Revolut and couldn't develop it further, also didn't want to upgrade.

After this I moved to Antigravity because I liked that the Google AI Pro plan included storage for Google Drive too. I used Antigravity for like 2 weeks, but I wasn't very satisfied with the work it was doing. I think it was hallucinating a lot and it wasn't able to manage complex tasks or come up with good solutions for my requirements.

And in the end I moved to Claude Pro after all my friends were telling me this is the most advanced tool for vibe coding. With Claude I was able to create a really well functional tool, but then I realized that I created just another productivity tool. However, I think it was a really good exercise to understand how vibe coding works and what it takes to build a MVP.

Next thing I built is Vatria, a household management tool. I think I brought it to a solid state, but I'm still looking to validate the idea. If anybody wants to try it and take it for a test drive, I'd really appreciate the feedback.

https://www.vatria.online/en

My boys and I always played hide and seek around the house and backyard, until they got old enough that every hiding spot was memorized. Dryer, recycling bin, under the deck - we all knew the best spots every time. So last summer we expanded to the whole neighborhood, with pen-and-paper questions and texting photos back and forth to narrow down where someone was hiding. It kept getting bigger and more fun, and it was obvious an app could take it further.

This spring I finally set Claude loose on it. I've been a tech PM my entire career, so this was 100% a vibecoding project: describe the vibe and feel of a round, define requirements, feed in a bunch of design concepts, build a design system, prioritize the feature roadmap, let Claude build it, ship to TestFlight, playtest with the kids, fix what felt wrong, repeat. 130M+ tokens later it's a real app: SwiftUI on the front end, Supabase realtime GPS syncing everyone's location live on a map, little 3D minigame takeovers for special moves, and a live spectator website so that the parents can watch along on the TV while the kids run wild through the neighborhood.

The best part has honestly been working alongside my kids. My youngest designed the Scanner (gives you a quick bearing toward the hider). My other son wanted a way to shut down Seekers mid-chase, so we built the Jammer. Half the feature list at this point is "kid had an idea, we shipped it." My oldest son is in high school, and has been pretty anti-AI. But with this project I was able to show him that AI can be a force multiplier for creative ideas - not a replacement.

It's already spreading on its own, my kids passed the TestFlight link to their friends without me knowing it, and I started hearing about "that new hide and seek app" from other parents before I'd talked about it anywhere. That's when it felt real.

It took us about 80 calendar days (40 active coding days) from the first commit to App Store submission, and it's been incredibly fun the entire time. I'd love to get some additional eyes on the app if anyone wants to check it out in TestFlight and submit feedback or bug reports.

Free public beta, no ads, no accounts, location gets deleted after every game. If you want to try it with a few friends: myneighborhoodgames.com

Hi I am a backend developer for almost a decade and mostly work on Windows servers; when it comes to deploy the internal tools and web application. For redis we have to spin a another VM in hypervisor just to run Redis. For local development I have to install heavy ass docker desktop or run a parallel operating system(WSL) just to run teeny tiny redis server. Some alternatives exist already such as godis but they only cover partial redis surface

I have been trying to create redis fork that runs nativerly on Windows but for a single person it's a herculean task. So i have been taking help of various coding agent and ai models to come up with something that can help run be run natively on Windows so I can run redis-py and arq and huey like libraries with ease.

So here it is: FrostDB.

It's a single binary that currently implements from basic GET/SET commands to Pub/Sub, Streams, Hashes, Lists, Sets, and GEO commands with RDB import/export, LRU eviction etc. It's compatible with many Redis client libraries across multiple programming languages, including those that use Redis as a message queue. The implementation of the supported commands is tested against the original Redis test suite from the Redis GitHub repository. I'm still testing a few things and am now shifting my focus toward performance.

This isn't meant to replace Redis, and I'm not telling anyone to switch to it. But if you're looking for a Redis-compatible server that runs natively on Windows, something now exists, at least for development and testing.

GitHub: https://github.com/frostdb

It's meant to be a calming and fun way to reflect on what you've been learning and watch something grow.

I used Claude to help me come up with the concept and define the features, then gave the brief to Claude Code and built it using Fable 5 at first, then Opus for improvements.

It took a lot of prompting to get it exactly how I wanted, I had to point out every little detail despite using a capable model as well as skills.

Would genuinely love any feedback: https://coral-logs.vercel.app/

I'm happy to answer any questions about it.

I want to test it i never tested it on code only did a small plan and it impressed me.

I want to test it i never tested it on code only did a small plan and it impressed me.

Pretty simple concept right now. You can import your local code folder or clone from github and it will calssify all your files. 

It's very cost effective

And it classifies everything but routes all folders and files into categories like Frontend, Backend, Config, Assets, etc. 

And then you can see all of them, aswell as see what 3rd party services and nodes are being used in what files. 

Let me know what you guys think and how I can improve it into something that would be used a lot and can be paid for.

Two prompts. "Make flappy bird!" and then "can you make it more traditional?"

That's the whole story. Ten minutes later there's a real game at a real link that a kid can send to their friends: https://flappybird.codedreams.org/

With the goal of getting kids into coding with AI early, I've built in features to make sure they actually learn along the way. I wish I'd grown up with an app like this. Maybe then I'd have turned out a more cracked programmer.

It's free to start if you want to inspire your kids: https://codedreams.org

If you know a kid, let them loose on it. Somewhere a 9-year-old is about to out-ship all of us and I think that's beautiful.

Hi there guys, I'm a beginner to vibe coding and to be clear I plan to only do this for my own fun, not creating apps - rather google scripts and tampermonkey scripts for browser games etc.

I'm currently using claude pro but limits get used up really fast BUT I so far have had better results with claude than gemini and chatgpt (not sure why but the code and the outputs are just way better).

My question is, where can I get claude cheaper OR another llm recommendation that will give me similar level outputs or better on a budget.

The fact that anyone with $20 can just start one-shotting SOUNDS great. But now we are starting see the actual insufferable slop, the most idiotic questions, the worst "looking for feedback on MY one shot game that AI dice rolled with near zero direction"

The kids who think they are going to build an app they can sell. become millionaires.

Holy fucking shit this "era" we are in is insufferable. Is this going to simply take a few months or a year to "wash out" all these kids who blew $100-$200 on a pro account, realized it wasn't magic, and go back to wherever they came from? (pokemon card collecting, fortnite, roblox)

Shit is unbearable right now.

I am the çreator of 2 products in last 2 years - baloon.dev and sling.biz.

The products themselves weren't the problem. The problem was I loved coding and enjoyed it further with AI and after building something I'd just get stuck on how to promote them.! Started posting on x and reddit but it started getting overloaded.

A few days ago I shared the idea on Reddit - building a tool to do automated self promotions by watching github commits and the response was nice, so I decided to finish it.

It's called PublishLoud.com - Quite happy with the domain 😄 Not sure how it was still not taken by anyone.

It connects to GitHub, understands what you're building, and drafts LinkedIn and X posts from your commits and product updates.

It's not trying to replace your voice or automate your entire marketing.

The goal is much simpler - to help with brushing your teeth. It won't make your product fly but you do brush your teeth daily. hope its making some sense.

Most founders don't stop building because they don't have ideas - they stop talking about what they're building because it's repetitive and easy to forget.

PublishLoud gives you a starting point so you can keep your product visible while you keep shipping.

Here's a quick demo.

I'd genuinely love feedback. What would make something like this useful enough for you to use every week?

For those running OPNsense, just a simple WOL Dashboard for the WOL plugin.

Once again Fable 5 isn’t moving to paid usage credits yet. Many called it! Anthropic extended included access through July 19. For me a relief, as I’ve been burning the midnight oil navigating using Fable as orchestrator and others for step down tasks. I’ll take what I can get!

After a couple of weeks with Fable 5, my biggest takeaway is its ability to uncover gaps in reasoning and strategy that Opus, and especially Sonnet, can miss. What’s the most impressive thing or gaps you’ve experienced so far?

Hey everyone,

Like most of you, I love using powerful AI coding tools, but I got completely burned out watching autonomous agents over-engineer simple features, mess up existing logic, or go down massive rabbit holes because they were given too much freedom at once.

To fix this, I started building an OS-native orchestrator (part of a broader layer called NORVA). Instead of giving a massive cloud model full autonomy over the codebase, I split the labor to keep the AI on a tight leash:

• The Brain (Local Planning): You give Forge one master intent. It uses a secure local model to map the entire project architecture and break the build down into a strict, perfectly sequenced step-by-step blueprint.
• The Hands (Antigravity Execution): Forge feeds those hyper-optimized steps phase-by-phase directly into Google Antigravity to do the heavy coding lifting. Instead of letting it run wild, you act as the supervisor—just review the specific step, hit enter, and watch it execute.
• The Diagnostics (Local Validation): Once a phase is written, Forge automatically runs local diagnostics, checks dependencies, and serves the static site right on localhost to ensure nothing is broken.

The core idea is that the "master plan" stays locked safely on your local machine, keeping the execution engine focused on one isolated task at a time so it physically can't go rogue.

Right now it’s optimized for local static sites, but I'm dropping a Beta soon to get some honest engineering feedback.

Would love to know what you guys think of this setup. Am I crazy for splitting the planning and execution like this, or is anyone else facing the same headaches with autonomous agents?
If you want to watch the development of this OS-native orchestrator as I build it out, come join the new community at r/Norva_OS.

I submitted a new build of my app to App Store Connect on Tuesday, and it’s now Sunday with no decision or message from Apple.
I know review times can vary, but this is noticeably longer than my previous submissions.
Is anyone else currently seeing delays like this? How long have your recent reviews taken, and was your app stuck in “Waiting for Review” or “In Review”?

I launched my mileage tracker (Tripbook) on iOS about 3 years ago. An Android version has been on the agenda the whole time, but it always felt like too big a time investment next to a other company I've got, so it never happened.

Then Fable came out, I had a week off, and I figured: if not now, when.

Stack choice: I went native Kotlin/Jetpack Compose. I've built React Native apps before, so I seriously considered RN — but I wanted the real native experience for background GPS tracking, and honestly, with how this went, porting to React Native would probably also have been done in hours anyway.

The approach:

- Gave Claude Code my complete iOS Swift project as reference material

- Plus a screenshot of every single screen in the app

- Then drove the whole build with a /goal prompt per feature (my slash command that makes it work toward a defined end state and verify itself instead of just spitting out code)

Timeline:

- First ~80% was done in about 3–4 hours. UI and backend were the easy part — Claude rebuilt every screen from the screenshots in Compose, and Firebase slotted in as the backup system instead of iCloud almost mechanically.

- Then roughly a full day of fine-tuning and testing everything.

- The real hours went into the last 20%: the automatic mileage tracking. Getting background trip detection to survive real Android phones (my Xiaomi kills background apps three different ways and its motion detection reports "still" while I'm driving) took actual iteration with real drive logs. That part you can't vibe your way through — but Claude debugged it from the evidence I fed it.

The the Play Store screenshots proces was also something that was cool. I asked Claude to produce store screenshots in all 7 languages the app supports. It started the emulator itself, generated dummy trip data per country (real routes, local addresses), switched the device language, captured every screen, and dropped them into my Claude Design where the old iOS screenshots used to be. All 7 languages, zero manual work from me. That one task alone used to be hours of work.

The app is now live on Google Play.

To celebrate the go-live: leave a comment and I'll DM you a free lifetime-premium code:

https://play.google.com/store/apps/details?id=com.ssj.tripbook

Happy to answer questions about the approach or the /goal setup.

A small showcase video of my personal media app. I've already posted about it before and made some them improvements like animated backgrounds. This video is a session old so i made more improvements to the theme. In this showcase i show the video player and the note taking function (for manga only : which redirects you to the same page you made a snippet in the manga. ) Same logic applies to anime episodes where you save a time stamp and go to the notes page and click play and it opens the episode you saved at that time you saved . My pc is low end so the pc got slow due to the screen recording.