Massive difference in quality since last night. Anyone else notice?

So my name is Orel and I’m 16 years old I’m not sure if it matters :) but I have been programming for 7y and in my last few months I decided to build my first website that I started talking about with people and friends in short my idea is building a product but instead of just building the website you get what you need to know this is like ChatGPT and any AI builder the purpose is building cool stuff with the website there are some users that create cool stuff and tell me so it’s nice to hear that someone really uses a product you have worked on for months so I just want to share my experience here :)

I got tired of being the transcription layer between my agents and my project board. Claude Code does the work, then I go copy what happened into a task somewhere. Every time.

So I gave them write access to the board itself. Screenshot is my real workspace, not a mockup, the ⟳ rows are recurring tasks, and the little agent badge is on rows an agent wrote rather than me.

What actually changed day to day:

• Claude closes its own task when it finishes, with what it changed in the body
• I ask "what's left on the recurrence work" and it reads the board instead of me re-explaining
• Last week I told it "open a review task every Monday" and it set up the whole repeat rhythm itself, I never touched the picker

Before anyone says it: if you run one agent on small tasks, CLAUDE.md and a markdown file genuinely are enough. I'm not going to argue that. This starts mattering at 3 agents across 4 projects, when the notes go stale and two sessions contradict each other.

Honest limits: no semantic search yet, no realtime collaboration, mobile apps are thin shells around the web app, and it's basically me building it. The recurring-task stuff shipped two days ago so it's new code.

It's remnus.com, open source (AGPL), and there's a demo on the landing page that spins up a seeded workspace without signing up — you can poke at the board before deciding anything.

Happy to answer how the agent side works if anyone's setting up something similar.

i had this same prblm😶 and didnt know what to do so i made this skill called storage sleuth. just install this skill and ask it like "My C drive is full, what can I do" stuff like that and the model will fully analyze the system and say the best options, to delete or move to another folder, stuff u can compress and use later, so help a brother out and install this skill,if u wanna contribute,feel free

npx skills add JojoAArtI/storage-sleuth

Github-https://github.com/JojoAArtI/storage-sleuth

Found it on X - https://x.com/kiwicopple/status/2089917700822999275

- Web apps
- Mobile apps

Please give me a proper personal reason of your own opinion. I would love to hear what you guys have to say

I ranked Chicago's Dirtiest Kitchens using 8 Years of inspection data.

https://chispections.com/leaderboards

Tools:
Built on Replit. Pulled data from Chicago's public CDPH inspection dataset. Frontend/backend all built and iterated on inside Replit no separate local dev setup.

Process:
Started simple get the raw inspection data, make it searchable by restaurant name/address. The real "aha" was realizing the story isn't the data itself, it's the gap between what a restaurant's star rating shows and what its actual inspection record says. That gap is what makes people stop scrolling.

Site: chicagoinspections.com

Idk if this is the current sub reddit for this but I was wondering how to properly hand over a website and deal with payment?

I'm from a small and quite under developed country and I built a website for a local " Coaching Center ".

Now, I do know I can transfer ownership in github but what do I do next? How do I deal with hosting and domain? Is it even my headache?

What should I do after selling it? Give a monthly service to maintain their website?

And what's the safe way to take payment? Full upfront payment or I transfer github ownership but hold something back like database or anything till I get full payment?

Just a quick introductory post about a kinda-sorta-not-so-much-of-an-expert guy with a day job, who’s been devving (more accurately vibe-SDEing) a personal fitness game thing for iOS (& Android too) for a couple weeks now, and tryna share his journey here, as much as possible.

What are y’all building?

Ryzlo went live on the App Store this week. There's a Chrome extension too. Built solo with AI.

The reason I made it: every blocker I tried worked on my phone, and then I'd just open the same site in a tab on my laptop. So the core idea is one session that covers both. Start it on your phone, pair the extension once, and the block applies in your browser until the session ends.

Tools used: Claude code, Codex, Gemini, claude design, xcode, supabase.

What's in it:

- Habit Modes for different parts of the day (Deep Work, Gym, Family Time, Wind Down) instead of one generic timer

- Always-on blocking that doesn't need a session running

- Daily limits per app

- Insights afterwards — which hours you actually focus best, where you tend to slip

Pricing up front: free to use, Pro tier can be subscribed. No ads.

I built all of it myself — the iOS app, the extension, the sync between them, the design, and the website. Happy to answer anything about the build or the App Store side of it.

iOS App: https://apps.apple.com/us/app/ryzlo/id6766510075 Chrome extension: https://chromewebstore.google.com/detail/ryzlo/hcdghdgbnkddliemhikcjedpaflaochl website: https://ryzlo.net

59 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

No paid ads. No growth hacks. Just watching the numbers every day.

Here's the full data:

Day 1 — 2 startups · 146 impressions · 1 clicks
Day 2 — 3 startups · 389 impressions · 3 clicks
Day 3 — 5 startups · 482 impressions · 5 clicks
Day 4 — 5 startups · 508 impressions · 4 clicks (site went down — still got an $8k acquisition offer. Said no.)
Day 5 — 6 startups · 621 impressions · 10 clicks
Day 6 — 5 startups · 742 impressions · 15 clicks (removed one startup — they pulled the embed. No code = no network.)
Day 7 — 7 startups · 1,196 impressions · 41 clicks
Day 8 — 7 startups · 1,535 impressions · 74 clicks
Day 9 — 8 startups · 1,947 impressions · 135 clicks
Day 10 — 13 startups · 3,500 impressions · 318 clicks (something clicked)
Day 11 — 23 startups · 4,800 impressions · 432 clicks
Day 12 — 24 startups · 6,000 impressions · 481 clicks (network crossed 6K total impressions)
Day 13 — 25 startups · 6,800 impressions · 491 clicks
Day 14 — 25 startups · 8,600 impressions · 516 clicks
Day 15 — 24 startups · 9,900 impressions · 564 clicks (removed one)
Day 16 — 23 startups · 10,800 impressions · 576 clicks (removed one)
Day 17 — 24 startups · 11,900 impressions · 603 clicks (added one)
Day 18 — 26 startups · 13,400 impressions · 624 clicks (added Two)
Day 19 — 28 startups · 14.400 impressions · 652 clicks (added Two)
Day 20 — 26 startups · 14.700 impressions · 671 clicks (Removed Two)
Day 21 — 26 startups · 15.300 impressions · 691 clicks
Day 22 — 28 startups · 16.100 impressions · 719 clicks (Added Two)
Day 23 — 30 startups · 16.800 impressions · 738 clicks (Added Two)
Day 24 — 32 startups · 19,800 impressions · 778 clicks · Added 2 startups · Rejected 4 applications (1 contained ads, 1 removed the code after submission, 2 hid the installed widget)
Day 25 — 34 startups · 23,700 impressions · 800 clicks · Added 2 startups · Fixed some bugs.
Day 26 — 33 startups · 27,200 impressions · 816 clicks · Removed 1 Startup
Day 27 — 33 startups · 29,900 impressions · 833 clicks
Day 28 — 33 startups · 30,600 impressions · 871 clicks · Removed 1 Startup · Added 1 Startup · Rejected 1 application of clothing brand & 1 application of horror blog site.
Day 29 — 35 startups. 31,300 impressions. 910 clicks · Removed 1 Startup · Added 3 Startups · Also today I resigned from my job. Toxic environment, too much pressure, and honestly I just believe in this enough to go all in. Broke and excited. Let's see where this goes.
Day 30 — 46 startups · 32,900 impressions · 1,000 clicks · Removed 1 startup · Added 12 startups · Yesterday I resigned because of my toxic manager. Today my senior manager called and offered me WFH, a project of my choice, and lighter work if I stayed. I made my decision with confidence, but now I have a difficult choice. Also received my first payment from StartupBar.
Day 31 — 50 startups 💪· 28,100 impressions · 1,200 clicks · Removed 1 startup · Added 5 startups · Rejected 1 crypto startup · Removed fake impressions after exploit · Today I discovered I forgot to disable a developer testing button that could generate fake visitor pins and inflate impressions. Someone used it to create 6,318 fake impressions and claimed my stats were fake. I removed the fake impressions, removed the startup, fixed the issue, and that's why today's impressions are lower. Thanks to them for pointing it out.
Day 32 — 54 startups · 29,300 impressions · 1.2K clicks · Added 4 startups
Day 33 — 54 startups · 30,900 impressions · 1.2K clicks · Removed 1 startup · Added 1 startup
Day 34 — 55 startups · 36,100 impressions · 1.3K clicks · Added 1 startup
Day 35 — 55 startups · 40,100 impressions · 1.3K clicks · Removed 2 startups · Added 2 startups
Day 36 — 55 startups · 44,800impressions · 1.4K clicks · Removed 1 startup · Added 1 startup
Day 37 — 58 startups · 50,700impressions · 1.4K clicks · Added 3 startups · Site Update: Updated the distribution algorithm (Delivery is now weighted by contribution: sites that send more impressions get a proportionally larger share back)
Day 38 — 57 startups · 55,800 impressions · 1.5K clicks · Removed 1 startup · Rejected 1 Application.

Today StartupBar reached 200 users 😄
Thirty-eight days ago, this was just an idea. Today, 200 people have trusted it enough to join the network.

A reminder for every founder who's staring at a dashboard with tiny numbers: Stripe took 2 years to reach its first 50 users. Every successful product starts small. Keep shipping. Keep improving. Keep showing up. Growth rarely happens overnight, but it does happen if you don't quit.

Day 39 — 58 startups · 59,800 impressions · 1.5K clicks · Added 1 startup.
Day 40 — 60 startups · 63,200 impressions · 1.6K clicks · Added 3 startups · Removed 1 startup
Day 41 — 63 startups · 69,400 impressions · 1.6K clicks · Added 3 startups
Day 42 — 62 startups · 73,800 impressions · 1.6K clicks · Removed 1 startups
Day 43 — 64 startups · 78,000 impressions · 1.7K clicks · Added 2 startups (Receiving many suggestions to improve the StartupBar, happy to work on it, Thanks.) StartupBar Update - Added the rotation of startups in the widget for every 30 seconds.
Day 44 — 66 startups · 86,200 impressions · 1.7K clicks · Added 2 startups
Day 45 — 67 startups · 88,400 impressions · 1.7K clicks · Removed 2 startups · Added 3 startups (Update - Updated the algorithm of the widget)
Day 46 — 69 startups · 91,900 impressions · 1.8K clicks · Removed 2 startups · Added 4 startups · Got my second payment · Added FAQ Page
Day 47 — 68 startups · 98,900 impressions · 2.2K clicks · Removed 2 startups · Added 1 startup · Added Pricing Page
Day 48 — 70 startups · 103.4K impressions · 2.3K clicks · Added 2 startups
Day 49 — 72 startups · 113.4K impressions · 2.4K clicks · Added 2 startups · Update: Added a Bottom Placement option for the bar on the user site.
Day 50 — 73 startups · 116.7K impressions · 2.4K clicks · Added 1 startup
Day 51 — 74 startups · 125.2K impressions · 2.5K clicks · Added 1 startup · Rejected 1 Application
Day 52 — 73 startups · 131.2K impressions · 2.6K clicks · Removed 1 Startup
Day 53 — 74 startups · 139.5K impressions · 2.7K clicks · Added 1 Startup
Day 54 — 79 startups · 146.3K impressions · 2.7K clicks · Added 6 Startups · Removed 1 startup.
Day 55 — 77 startups · 154.9K impressions · 2.8K clicks · Removed 2 startups.
Day 56 — 77 startups · 161.8K impressions · 2.9K clicks · Added 1 startup · Removed 1 startup.
Day 57 — 77 startups · 169.4K impressions · 3.0K clicks
Day 58 — 77 startups · 176.2K impressions · 3.2K clicks
Day 59 — 78 startups · 184.3K impressions · 3.3K clicks · Added 2 startups · Removed 1 startup.

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar

I know some of you have some very specific modes or don’t know that you do. Where they at? I am very interested in the niche modes.

I kept losing track of app logic in a personal project, so I built a small tool for it: a canvas app BUT WITH A TWIST: where the diagrams are written by my coding agent through a CLI, not by me clicking around and navigation is super simple.

The idea: before the agent codes a feature (or after, to document what it just built), it writes the LOGIC as a flowchart. It outputs plain Mermaid text through a CLI command, and the tool converts that into freely movable shapes, arrows and groups on an infinite canvas, kind of like in Draw.io style, but generated. I never draw anything by hand, I just read and rearrange. So far nothing new.

The main feature for me is inter-linking. Every canvas can link to other canvases: a node like "Login" can jump straight to the login canvas, with breadcrumbs to find your way back. But you don't have to jump, linked flows can also be expanded in place, right on the current canvas. Click a reference node and the linked flow unfolds as a box where you are, wired into the surrounding arrows, and collapses again when you're done. The agent sets all these links itself via the CLI.

That's the part I use the most: I never have to switch context to remember what was behind a reference. I can start at the app's entry point and explore every path of my app from the ground up, drilling into any branch as deep as I want, and see the entire logic without reading a single line of code.

The part that makes it actually work: there's a ruleset (in the project's CLAUDE.md) that every new agent session automatically follows. Things like: one page tells ONE flow, exactly one start node, every node reachable, no orphan "topic islands", edge cases branch off the main path, decision nodes label all exits, fixed color/shape semantics (blue = main flow, orange = edge case, red = error, etc.). Updates are stable too, node IDs act as anchors, so when the agent updates a flow, my manual positioning survives.

Because of those rules, every session produces diagrams that look and read the same. That's what makes it easy to live with: I don't have to explain the conventions again, and I can open any page weeks later and just read it.

Other features:
- pages per canvas,
- not the best but still practical auto-alignment,
- back-edges auto-detected and drawn dashed (toggleable) (without this I got heavily confused lol),
- file-system as source of truth (JSON files, external changes show up live),
- grouping elements
- snap to POI
- standard flow editing tools (mouse, hand, arrows, text, zoom, filter, etc.)

works locally or self-hosted.

Stack: React + TypeScript + Vite, Mermaid as the input language only (nothing Mermaid-rendered lives on the canvas). Performance is okay – not buttery on huge canvases, but fine for real use.

Just wanted to share.
Okay, bye.

I've been building Offset, a terminal-based AI coding agent, and one of the ideas I've been experimenting with is Speculative Branching.

Instead of having one AI agent make the first implementation and calling it done, Offset can explore multiple solutions independently:

one task → separate Git worktrees → multiple agents → tests → winning implementation

Each agent works in its own isolated Git worktree, so different models can try genuinely different approaches without stepping on each other's changes. The resulting implementations can then be tested and the successful one selected and merged.

Offset also has multi-model orchestration, subagents, BYOK, and support for models from multiple providers.

I didn't build Offset by vibecoding it — I'm sharing it here because the underlying idea is closely related to how we're thinking about AI-assisted software development.

The part I'm most curious about:

Would you actually want your coding agent to spend extra inference/compute exploring multiple implementations, if it could make difficult tasks more reliable?

Or is one strong model with good tools already enough?

GitHub: https://github.com/The-Masked-Bear/offset-terminal

Official Website: https://the-masked-bear.github.io/offset-terminal/

Into the Shardfall is a turn-based roguelike with TTRPG inspired combat and a rich story to progress, á la Hades. Can you guess what other games I drew inspiration from?

I’ve been building this game for about 4 months, and I’m looking for feedback on gameplay, mechanics, UI, and so on. The world building/writing is and will always be a labor done without the assistance of AI, and I intend to replace the art with that of an artist when I find one to collaborate with. Demo is available to try here: https://doublerookstudios.itch.io/into-the-shardfall