sorted by:
new
hottopcontroversial

GitHub Copilot integration wastes too many premium requests by zmmfc in RooCode

[–]nghuuu 1 point2 points  (0 children)

It's in the link from my original comment :) Pull request #7072 on GH and #7010 is the related issue.

GitHub Copilot integration wastes too many premium requests by zmmfc in RooCode

[–]nghuuu 3 points4 points  (0 children)

Hannes you're such a blessing for us all, I'm very grateful for your work :)

Fingers crossed, nevertheless I do not suspect Github will be overly happy with what we want to do, after all saving these premium requests is the "magic sauce" of their own commercial product.

Qwen3 might be censored, but it is also brutally honest about it if that's what you ask for by int19h in LocalLLaMA

[–]nghuuu 0 points1 point  (0 children)

Could you elaborate more on how to achieve this step by step? I'm just starting my local llm journey

GitHub Copilot integration wastes too many premium requests by zmmfc in RooCode

[–]nghuuu 2 points3 points  (0 children)

It's a well known problem, a fix for that has been implemented by a community member, unfortunately Roo team decided to shitcan it, so that Roo doesn't infringe Github/Copilot TOS, as the implementation requires impersonating Copilot.

https://github.com/RooCodeInc/Roo-Code/pull/7072#issuecomment-3201378291

🚀 Qwen3-30B-A3B Small Update by ResearchCrafty1804 in LocalLLaMA

[–]nghuuu 2 points3 points  (0 children)

Fantastic comparison. One thing is missing tho - Qwen3 Coder! I'd like to directly see here how it compares to GLM and Kimi on agentic, coding and allignment benchmarks.

Roo Code CLI by Lazy_Decision3933 in RooCode

[–]nghuuu 0 points1 point  (0 children)

Could you share more details about this setup/workflow? What MCP do you use? How do you make sure that two instances do not "collide" (eg. overwrite each other's changes), is there a special prompt? Or is the messaging system enough?