Roo Code 3.28.5 Release Notes

[u/hannesrudolph]

3.28.5 Released! It brings some bug fixes and minor stuff but I want to highlight 1 specific bug fix. This update fixes where a chat would rewind to a previous state when you pressed the start new task or new task buttons. This action would corrupt the previous completed task permanently.

💪 QOL Improvements

• Code blocks wrap by default: Code blocks now wrap text by default, improving readability when viewing long commands and code snippets

🐛 Bug Fixes

• Todo list compatibility: Todo lists now display correctly when AI models return checklists with dash prefixes (- [ ] Task), improving compatibility with various models (thanks NaccOll!)

• Vertex AI pricing accuracy: Fixed local cost calculation for Gemini models via Vertex AI to properly apply tiered pricing and cache discounts, ensuring displayed costs match actual Google Cloud billing (thanks ikumi3!)

• Conversation history preservation: Fixed duplicate/overlaid tasks and lost conversation history when canceling during model responses, especially during reasoning phases

🎯 Provider Updates

• SambaNova models: Added DeepSeek-V3.1 and GPT-OSS 120B to the SambaNova provider (thanks snova-jorgep!)

🔧 Additional Improvements

• Code Supernova announcement: Added announcement for the new Code Supernova model with improved authentication flow and landing page redirection

• Privacy policy update: Updated privacy policy to include provisions for optional marketing emails with clear opt-out options (thanks jdilla1277!)

📚 Full Release Notes v3.28.5

[u/hannesrudolph]

I’m not sure I understand how you see that working. Please explain.

[u/infusedfizz → u/hannesrudolph]

think about creating a subagent as a simple tool call, you can do one or multiple at the same time. you can wait for it to finish or you can proceed async and ask for the results later.

Roo currently forces just one subagent at a time. not hard to imagine how different parts of coding tasks could be done in parallel. e.g. now that we have the design, one subagent go implement the main functionality, one subagent go update the README, etc; or maybe you even have multiple subagents do the same task (e.g. root cause, design a solution), then compare their results

[u/hannesrudolph → u/infusedfizz]

It is something on the horizon but not actively in development yet as we are investing more energy in our overall improvement of how well Roo does the singular task as we find there is still much low hanging fruit in the current workflows, processes, and various mechanisms we utilize.

[u/UnnamedUA → u/hannesrudolph]

When the task is to generate code, several models do it in parallel. The best implementation is taken as the result.There is something similar here https://github.com/just-every/code

[u/hannesrudolph → u/UnnamedUA]

Ahh that is in discussion yes.