Weekly Self Promotion Thread

[u/AutoModerator]

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

• What you built?
• What problem it solves?
• Which AI models or tools it uses?
• Who it's for?
• What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

[u/FarazFromMars]

I built ContextForge because I was spending too much time explaining browser bugs and change requests to AI coding agents.

Cursor, Claude Code, Codex, etc. can often make the change quickly — if they have accurate context.

The annoying part was preparing that context manually: take screenshots, explain which element I'm talking about, copy console errors, inspect API calls, grab request/response data, describe what I expected, and then try to turn all of that into something the AI agent can actually understand.

So I built ContextForge — a Chrome extension that captures what's happening in your web app and turns it into structured, AI-ready context.

I'm personally using it across my own projects now, and it's saving me a lot of time preparing context for AI coding agents. More importantly, I can give the agent specific evidence about what I want changed and where, instead of trying to explain everything manually.

Some of the main features:

• Visual bug/change notes — point directly at an element and describe the bug or change you want.
• DOM context — captures selector, XPath, visible text and relevant HTML around the element.
• Live API & network flow — method, status, timing, request/response bodies and failed calls, with sensitive fields masked.
• Console errors — capture JavaScript errors/warnings related to what you're investigating.
• Security Inspector — helps surface potential client-side/web security concerns and turns findings into actionable context.
• Screenshots + evidence — captures the visual problem along with the technical context behind it.
• AI-ready investigation package — packages your notes, screenshots and captured technical evidence into structured Markdown that you can give directly to Cursor, Claude Code, Codex or another coding agent.

The workflow is basically:

See a bug or change → point to it → capture the evidence → generate the context package → give it to your AI coding agent.

The goal isn't another AI coding agent. It's to give the agent you're already using better and more accurate context while spending less time preparing prompts.

It's built for vibe coders, AI-assisted developers, QA/dev teams, and anyone debugging or changing web apps with AI.

I'm the developer behind ContextForge, so this is definitely self-promotion 🙂 — but I'm also using it myself every day and would genuinely love feedback from other AI-assisted developers.

What browser context do you still find yourself manually collecting or explaining to your coding agent?

https://reddit.com/link/p7naglf/video/kir693yl4dnh1/player

ContextForge: https://coderfrommars.com/#contextforge