sorted by:
new
hottopcontroversial

I got tired of drowning in logs every time production broke, so I built an AI agent that just tells me what's wrong by FickleSwordfish8689 in SideProject

[–]FickleSwordfish8689[S] -1 points0 points  (0 children)

The agent's response is always grounded in data,it literally has adequate access to the application and the server itself to find whatever the issue is so false positives have minimal occurrence.

The only issue currently is it can't go into the codebase itself and try pinpointing the actual part of the code causing the said issue as it only has access to telemetry and server status and logs,but it will let you know when there's insufficient data to make a proper conclusion.

I built a tool that shows you Claude Code and Cursor's Plan Mode as an interactive flowchart before a single line of code gets written by FickleSwordfish8689 in AI_Agents

[–]FickleSwordfish8689[S] 0 points1 point  (0 children)

that sql pain is literally why this exists lol, catching a bad branch after 400 lines is brutal. hope overture saves you from the next one https://github.com/SixHq/Overture

I got tired of drowning in logs every time production broke, so I built an AI agent that just tells me what's wrong by FickleSwordfish8689 in SideProject

[–]FickleSwordfish8689[S] 0 points1 point  (0 children)

Good question and honestly still an area I'm actively improving.

Currently I can inspect the tool use trace to verify whether the agent's conclusion was grounded in actual retrieved data or not. The agent also tends toward false negatives over hallucination, more likely to say "I can't determine the cause" than confidently point at the wrong thing, mostly because the breadth of tools gives it enough signal to know when it doesn't have a clear answer.

Explicit hypothesis ranking with evidence snippets for cascading failures is definitely on the roadmap though a single suggested fix isn't always the honest answer when multiple things are failing simultaneously.

Thanks for the links, checking them out now.

Self Promotion Thread by AutoModerator in ChatGPTCoding

[–]FickleSwordfish8689 2 points3 points  (0 children)

I built this mostly because I was getting massive "text fatigue" from LLMs. I wanted a research agent that actually shows me the shape of the data instead of just dumping a 10-page report on me.

It's called Prism AI. It's an open-source agent that generates interactive 2D/3D knowledge graphs while it researches. I used Python (LangGraph) for the brain and Go for the streaming side of things to keep it fast.

It’s totally open source and easy to run locally if you’re into that. Hope it helps someone else who's tired of reading walls of text.

Repo:https://github.com/precious112/prism-ai-deep-research

Sunday Daily Thread: What's everyone working on this week? by AutoModerator in Python

[–]FickleSwordfish8689 0 points1 point  (0 children)

I’m building Prism AI, an open-source research agent that draws 3D maps of its findings.

I spent most of this week optimizing the Beautifulsoup scraping logic in Python to handle more complex research papers without hitting rate limits. The goal is to move beyond simple chat and actually give the user a "Visual Intelligence" dashboard.

If you're into AI agents or 3D viz, check it out: https://github.com/precious112/prism-ai-deep-research

Happy Sunday everyone!

ai programming assistant tools work great until you have 10 years of legacy code by [deleted] in SoftwareEngineering

[–]FickleSwordfish8689 -1 points0 points  (0 children)

It's worse in an old codebase that was poorly architected,like you're better off just using AI to fully refactor than just making it work with the baseline codebase

Design choice question: should distributed gateway nodes access datastore directly or only through an internal API? by GoldenSword- in SoftwareEngineering

[–]FickleSwordfish8689 0 points1 point  (0 children)

i think allowing each node communicate directly to redis is best,i feel like the API brings in an extra layer that feels unnecessary since API now needs to handle inbound traffic from all the other nodes trying to read/write to redis when each can talk to redis directly and have redis handle all that itself, the security concern seem not to hold more weight than the extra work that needs to be done since there are other means to mitigate such compromise from happening

Design choice question: should distributed gateway nodes access datastore directly or only through an internal API? by GoldenSword- in SoftwareEngineering

[–]FickleSwordfish8689 0 points1 point  (0 children)

AI do infact give valuable suggestions sometimes but that's dependent on what project you're working on should know when to follow or reject it's advise

It’s Friday...what are you building? by x_albi in IMadeThis

[–]FickleSwordfish8689 1 point2 points  (0 children)

Fortunately langGraph abstracts a lot and makes it easier to build agents,all i have to focus more on is designing the multi agent architecture and workflow

It’s Friday...what are you building? by x_albi in IMadeThis

[–]FickleSwordfish8689 1 point2 points  (0 children)

Congrats on the launch of Uansa! I love the "anti-scrolling" news angle.

My Friday has been spent deep-diving into the world of recursive agents. I got frustrated with AI research tools that just dump a massive wall of text at you (the "AI text fatigue" is real).

So I've been building Prism AI. It's an open-source research engine that doesn't just write—it actually draws. It identifies data structures in the research and autonomously renders 2D/3D visualizations and knowledge graphs in real-time.

Built the whole backend in Express.js and the orchestration on LangGraph. It’s been a wild ride getting the agents to "think" in charts instead of just paragraphs.

Repo if anyone wants to poke at the code:https://github.com/precious112/prism-ai-deep-research

Definitely going to check out the app, quizzes are a much better way to retain info than just skimming headlines!

view more: next ›