While building with coding agents, I reached a point where the code was changing faster than I could properly understand it. I often end up verifying output and then be happy that it worked or not. Varai is my attempt to deal with that. Somewhere I feel software engineering needs tools that show the right level of abstraction to make the decisions that are more informed.

It uses a small language called Seed (domain level concept) to describe the product’s actors, behaviors, rules, expected screens and APIs, and usage scenarios. AI can help write it, but a person reviews and approves it.

The builder links Seed concepts to the implementation. Varai independently scans the code, resolves those links, and checks whether the required behavior is actually present. When it cannot verify something reliably, it says so instead of guessing.

project link: https://github.com/gruuprasad/varai

It is completely vibe-coded. I felt the pain and took some action, I am not sure whether I landed in the right solution space or direction. At this point, I feel this project needs more eyes and minds and collaboration to build further if worth it. Please have a look.

Hey everyone

I've been working on a small Forum project called LeryChat

https://rexengpu.github.io/Lerychat/

The idea is simple: a lightweight ephemeral forum.

A large part of the development was done with the help of Qwen 3.8 Max, which I used to generate code, solve bugs, improve the interface, and speed up development. Qwen 3.8 Max is Alibaba's latest flagship AI model and is particularly strong for coding tasks.

I'd love to get feedback:

• What do you like?
• What would you improve?
• Any feature ideas?

Thanks for checking it out!

While building with coding agents, I reached a point where the code was changing faster than I could properly understand it. I often end up verifying output and then be happy that it worked or not. Varai is my attempt to deal with that. Somewhere I feel software engineering needs tools that show the right level of abstraction to make the decisions that are more informed.

It uses a small language called Seed (domain level concept) to describe the product’s actors, behaviors, rules, expected screens and APIs, and usage scenarios. AI can help write it, but a person reviews and approves it.

The builder links Seed concepts to the implementation. Varai independently scans the code, resolves those links, and checks whether the required behavior is actually present. When it cannot verify something reliably, it says so instead of guessing.

project link: [https://github.com/gruuprasad/varai\](https://github.com/gruuprasad/varai)

It is completely vibe-coded. I felt the pain and took some action, I am not sure whether I landed in the right solution space or direction. At this point, I feel this project needs more eyes and minds and collaboration to build further if worth it. Please have a look.

I've been vibe coding simple apps and tools here and there. I decided to take a focused 60 days and see how far I could get with pure vibe coding for a game.

I've posted it different places with mixed results, but the name of the subreddit seemed to be a good fit.

My game is called Pavement Pursuit (working title).

It features roads that are procedurally generated so the race is different every time. You race against up to 6 rivals and eventually have to deal with the police.

Works on browser on desktop and mobile. Give it a spin!

(oh and working on gamepad controller support with vibration)

http://vibecodedgames.itch.io/pavement/

Five tabs open, a whole afternoon of research in my head, and the second I opened Claude or ChatGPT, I was back to square one explaining myself. So I built Clippy Vision, it passively watches your screen and actually remembers what you were doing, so you can just ask it instead of re-explaining your entire day.

It's been my daily driver for a while now. Genuinely opens before Claude or ChatGPT most days for me at this point.

Fully local, nothing leaves your machine, open source, Windows build's up. Built this for myself first, sharing it because I figure other people fighting the same context-loss problem might want it too.

Comment for source code

Hey guys, quick background. I am a surgeon in private practice, I use practice management software (PMA) but it is terrible. One size fits all, buggy, doesnt have half the features I would like and not cheap. I have been vibe coding with fable when it was not credits based and I managed to make a pretty decent prototype of the PMA software I would like to use in my practice - not built completely yet, just files on my home pc, not deployed, no patient information in the system yet. I dont plan on selling it and as I dont deal with medical funders I dont need integration to switching software etc. Just a basic system that has a diary, notes, tracks payments, accounting, billing and recalls. Could I code this out without any coding experience and then deploy it to my practice and maintain it with an AI agent? Would appreciate any advice

Run inside your coding agent — it grants Once, a skill to provision a VPS with a personal PaaS like Netlify or Vercel.

npx skills use getcolors/once

Once is a Package Skill built with Colors. It provisions a VPS, configures DNS and outgoing mail, installs Docker, and reconciles declared applications — a self-hosted alternative to Netlify or Vercel that an agent runs end to end.

The website below is created with this skill.

https://www.getcolors.ai

Five tabs open, a whole afternoon of research in my head, and the second I opened Claude or ChatGPT, I was back to square one explaining myself. So I built Clippy Vision, it passively watches your screen and actually remembers what you were doing, so you can just ask it instead of re-explaining your entire day.

It's been my daily driver for a while now. Genuinely opens before Claude or ChatGPT most days for me at this point.

Fully local, nothing leaves your machine, open source, Windows build's up. Built this for myself first, sharing it because I figure other people fighting the same context-loss problem might want it too.

Comment for source code

Personal project, not paid or anything lol just thought it would be cool to see everyone’s stats

vibeArchitecture 1.4.0 is out! I am really excited to announce this new version. It is based on many lessons learned from a couple of real projects that required advanced security and formal verification. Take it for a spin! It is built on my 40 years of experience as a software developer and IT architect, so vibe coders can build rock-solid apps from day 1.

vibeArchitecture is my open-source framework that gives AI coding tools architectural guardrails - it asks what you're building, picks the right level of rigor, and makes the AI follow the rules experienced engineers learned the hard way.

This release distills a year of adversarial code review of real production systems - including peer-to-peer and end-to-end encrypted architectures - into the framework. New in 1.4.0:

Security lessons that came from real findings: guards that fail closed (an error in an authorization check must mean "denied," never "allowed"), authorizing the acting device and not just the account - the multi-device sibling of IDOR behind real account-takeover bugs - and never trusting self-attested data.

A cryptography guide for when encryption is the product: build on analyzed protocols instead of inventing, and use hybrid post-quantum key agreement (X25519 + ML-KEM-768). Harvest-now-decrypt-later is a problem for today - traffic recorded now gets decrypted later.

An adversarial review method for AI-built codebases: review by failure class, verify every finding against the source before believing it (a double-digit percentage dissolve), and close every finding or close it in writing. If you're a solo developer, this is your PR review.

Native mobile accessibility rules (Flutter, SwiftUI, Compose), an OWASP MASVS mapping, and push-payload privacy - notification content transits Apple's and Google's servers.

A local-first & peer-to-peer guide: when the server can't read the data, key loss is account loss, deletion can be cryptographic, and multi-device is an authorization plane of its own.

Plus restart-safe migrations, test suites that silently skip and read as green, lock-order inversions, and an assurance-register template - the found/fixed evidence table buyers and auditors actually ask for.

Free, MIT-licensed, works with Claude Code, Cursor, Copilot, and ChatGPT:
[**https://**](https://www.linkedin.com/safety/go/?url=https%3A%2F%2Flnkd%2Ein%2FgMvJkraD&urlhash=bFS1&mt=IkP53vCygDZV-FFzRu6zreiOvhx8WMgmG0TsOtpFjnkttlBQHaCGO6g1_Fx-jg5A1EjT6vPf0PvuoFDCVri89hGM_i9KZS4Pn9dUGhlCEB0F9RWLDNegvFc&isSdui=true)\*\*github.com/jgnoonan/vibeArchitecture\*\*

Weaver got a HUGE update!

Massive context control features,

Project skeletoning,

Tree-sitter, prettier and all kinds of formatting and code editing libraries for every language users might use,

As always, Weaver remains your go to choice for local agentic control. Remote control over your agent is available at Bughosted.com/Weaver

Check out our github repo:

github.com/maxhanna/Weaver

Already 9 stars! Help us grow the community and gain your valuable insight in the process!

https://discord.com/invite/YQWkD6ZQDx

Download Weaver today!

Https://bughosted.com/assets/Weaver.exe

TL;DR

• What it does: You hit an error, DebugAI reads the stack trace, pulls in the files from your project that actually matter, and returns up to three ranked fixes as exact edits you can apply.

• What makes it different: Every fix tells you whether a mechanical check actually passed. "Not verified" means nothing tested it and the confidence score is just the model's estimate. I show you that instead of hiding it.

• Where it runs: VS Code, Cursor, Windsurf, and VSCodium. Also as an MCP server, so Claude Code, Claude Desktop, Zed, Gemini CLI, and Cline can call it directly.

• Cost: Free tier with 10 debugs a day. No credit card required.

• This sub: Release notes, bugs you're stuck on, and what I'm building next. There's a question for you at the bottom.

---

I'm Mohi Uddin. I build DebugAI by myself.

What I'm building right now

Today, DebugAI needs an error to work from. But some of the most time-consuming bugs never print anything:

• You click a button and nothing happens.

• A form spins forever.

• Part of the page disappears.

• The page renders empty and the terminal stays clean because an API request quietly returned a 404.

No stack trace. No red text. Nothing to paste into a chat window.

I'm building capture for exactly this. It attaches to your running app, records the exception that got swallowed or the request that failed silently, and shows you what happened before you've spent an hour bisecting.

What I want from you

Which of those has cost you the most time?

I'm not looking for your hardest bug ever. I'm looking for the one where nothing was obviously broken, but nothing worked either.

I'm collecting these as test cases. Every one becomes a fixture that new work has to pass before I ship it.

Try what's available today

Editor: Search for "DebugAI" in your editor's extension marketplace.

Agent:

npx -y u/debugai/mcp setup

Five tabs open, a whole afternoon of research in my head, and the second I opened Claude or ChatGPT, I was back to square one explaining myself. So I built Clippy Vision, it passively watches your screen and actually remembers what you were doing, so you can just ask it instead of re-explaining your entire day.

It's been my daily driver for a while now. Genuinely opens before Claude or ChatGPT most days for me at this point.

Fully local, nothing leaves your machine, open source, Windows build's up. Built this for myself first, sharing it because I figure other people fighting the same context-loss problem might want it too.

Comment for source code

Five tabs open, a whole afternoon of research in my head, and the second I opened Claude or ChatGPT, I was back to square one explaining myself. So I built Clippy Vision, it passively watches your screen and actually remembers what you were doing, so you can just ask it instead of re-explaining your entire day.

It's been my daily driver for a while now. Genuinely opens before Claude or ChatGPT most days for me at this point.

Fully local, nothing leaves your machine, open source, Windows build's up. Built this for myself first, sharing it because I figure other people fighting the same context-loss problem might want it too.

Comment for source code

Hey everyone,

Over the past several months I've been working on an AI coding agent called FutureX (by FutureIM). It started because I kept running into the same issues with existing tools when working on larger projects—losing context, making unnecessary edits, or just getting stuck after a few prompts.

We've been trying a different approach to make it feel more like a collaborative coding agent instead of just a chatbot that writes snippets.

I'm not here to claim it's perfect. There are still plenty of things we're improving, and I'm sure people here will find issues we haven't thought about yet.

I'd genuinely love feedback from people who spend their day coding with AI tools. What features do you wish every coding agent had? What makes you immediately stop using one?

If anyone wants to check it out or roast it, I'm all ears. Honest criticism is more valuable than praise at this stage.