Developer Tools4 days ago
Odd Eye — Understand your code before asking AI to fix it
Understand code flow and app connections before asking AI to help modify your app.
@minmuner_devlog · X
Thanks for the feedback; I’m open to anything.
The full gallery
Tech stack
60 projects
Understand code flow and app connections before asking AI to help modify your app.
@minmuner_devlog · X
Thanks for the feedback; I’m open to anything.
AI agents build API integrations and automatically repair them when they break.
@getselfheal · X
SelfHeal - integrations that fix themselves. Vendor changes their API at 2am? The agent rewrites the connector, tests it, redeploys. You sleep. Demo (it breaks + heals on camera):
Scan and monitor AI-coded apps for security, performance, and code quality issues.
@Vibedoctor_io · X
Connect VibeDoctor MCP to Cursor, Copilot, Claude Code or Windsurf. Your agent gets a security gate built in. #ClaudeCode #AppSecurity #DevTools
Audit your AI app for security, privacy, and governance readiness.
u/Budget_Lawfulness_33 · Reddit
I made a tool that bridges the gap between vibe coding and actually knowing what you shipped A lot of people are shipping things they don’t fully understand anymore. With the new flagship models such Claude/Codex and people spending hundreds on AI subscriptions to build faster, apps are being shipped quicker than ever. But when you’re constantly throwing prompts at AI, adding features, and moving fast, it’s easy to lose track of what actually made it into your codebase. So I built: https
Scan your AI bills to find waste and prove savings with tamper-evident evidence.
@askrashidkhan · X
Notes with code blocks, Kanban bug tracker, and snippet library with GitHub import.
@SinghApurv1711 · X
Hey! Check it out here:
Review production agent traces to identify and fix recurring failures.
@guru3s · X
IMF team for when your AI agent ( Ethan Hunt ) is about to fail v0 at
Retries failed Stripe charges and recovers subscriptions with automated dunning sequences.
@Holdfast_app · X
Convert CVE data into machine-readable risk signals for AI agents and automation.
robert_marshall5 · Product Hunt
attestd CVE and supply chain risk signals for autonomous AI agents.
Free website analyzer & SEO audit tool — scan any site for performance, SEO, security, accessibility & UI/UX issues in 60 seconds. Fix what hurts your ranking.
@WebScore_now · X
Write and run code in your browser with AI code generation and auto-fix features.
@anish2good · X
Capture UI elements with code context and screenshots to share with AI agents for debugging visual bugs.
Loerei · HN
I found that describing where a broken UI is and taking screenshots for AI agents really sucks. I’m too lazy to explain an indescribable visual bug or capture a millisecond-long flash. I also don’t want to remember which file defines an element, whether it's right in the .tsx or a problem with the Parent Styles in .css. And even if you can point out the exact file, your agent still has to dig through thousands of lines of code to know what on earth you're yapping about. In a 7700-file monorepo like Cal.com, simply giving the right file in the prompt for your agent saves about 68.9% of execution time and 94.2% of the tokens your agent needs to digest. HoverSource gives all the needed information and further pushes it to -88.5% time and -94.5% tokens, basically skipping the entire digging session and jumping straight to reasoning and executing. The save is linear to how big your codebase is. I want to save tokens, but don’t want to spend my time and energy digging manually, and a junio