🚀 Smarter Debugging for Roo – Save Time, Save Tokens, Without Headaches! 🛠️

[thelege2nd]

Let’s make Roo a better debugger! If Roo could automatically receive feedback from tools like ErrorLens, it would catch mistakes faster, reduce unnecessary token usage, and make debugging way more efficient. Right now, Roo often wastes time and tokens trying to figure out errors that debugging tools already detect instantly. By integrating this feedback loop, we can improve accuracy and streamline the debugging process. This would really take Roo to another place. Vote to make this happen! 🔥

@mrubens

[Unnamed2025]

Instead of a 3rd party plugin, it can check the errors in the "problems" tab in VS code

[cfdude]

does it not already do this?

[bramburn]

could run a check with LSP for known programming languages.

[bramburn]

It doesn't get error logs from vscode' own lsp

…

On Fri, 14 Feb 2025, 18:56 Rob Sherman, ***@***.***> wrote: does it not already do this? — Reply to this email directly, view it on GitHub <#940 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUTT3O2T35P23P6AOTZKGL2PY36JAVCNFSM6AAAAABW5AVXHKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRQGQ3DCNY> . You are receiving this because you commented.Message ID: ***@***.***>

[robertheadley]

I have that that Roo being able to receive communication from other extensions would be extremely powerful. I support this idea.

[hannesrudolph]

I think this is already the case to a degree using the problems pane. If you would like any adjustments to the current implementation please submit a detailed feature proposal at https://github.com/RooCodeInc/Roo-Code/issues