Issue with Kilo Code Orchestrator Mode in DeepSeek 3.1 – Fails to Split Tasks Properly #2580
Unanswered
kenken1985
asked this question in
3. Q&A / helpdesk
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've been noticing some issues with the Kilo Code Orchestrator mode in DeepSeek v3.1. It appears that the orchestrator is no longer effectively breaking down tasks into smaller subtasks as expected.
Instead, it either:
This behavior often cause the task to be to big and cause the overthrow the context limit. It worked more effectively in earlier versions, so this seems like a potential regression.
Has anyone else experienced similar behavior? Any suggestions or workarounds?
Beta Was this translation helpful? Give feedback.
All reactions