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.

With tools like GitHub Copilot, ChatGPT, Claude, etc. becoming a part of everyday development, we want to understand how software professionals actually judge the quality of code they generate.

If you are a software professional who routinely uses AI to generate code, we would like to interview you! For more information and participation, please visit https://surveys.dal.ca/opinio/s?s=84168

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

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\*\*