I got tired of copy-pasting scattered logs to AI, so I built an open-source Go daemon that traces E2E (React to SQL)

Hi DEV Community! 👋 Like many of you, I rely heavily on AI (Claude/Cursor) for debugging. But recently, I noticed a huge pain point in my workflow: AI constantly hallucinates or gives generic answers when it lacks actual runtime context. Think about this common scenario: Your frontend crashes and throws a cryptic error in the browser console. However, the backend silently returns a 200 OK, or maybe there's a deep SQL constraint failing that the frontend never sees. To give the AI enough context to actually fix the bug, I had to: Manually collect logs from the browser console. Dig through the backend terminal to find the executed SQL. Check the Network tab for HTTP headers. Paste everything together into a massive prompt. It’s incredibly tedious, context-switching is draining, and it burns through tokens. 💡 The Solution: Trace2Prompt I decided to scratch my own itch and built Trace2Prompt—an open-source tool written in Go. thuanDaoSE / trace2prompt Zero-Config AI Debugging Assistant. Au