ragleap-core v0.13.6 was published on 2026-11-18. It fixes two bugs in the agents that were found by the first real-model test of sub-agents, run on a live server. Sub-agents stay off by default, and upgrading switches nothing new on. Source: the v0.13.6 release notes, checked on 2026-11-19.
What did the first real-model test of sub-agents find?
Two bugs. When v0.13.4 added sub-agents, they had been tested only with scripted models (see the v0.13.4 post). This is the first test with a real model, and it found the two bugs below. A re-test after the fixes is planned right after this release and has not been done yet.
What happens now when a sub-agent needs no tool?
Before, a child run that used no tool returned only "0 step(s): no actions", so the parent got nothing useful and delegated the same task again. The child now answers the task itself with one short model call, and that answer goes back to the parent (#1473).
What does ACTION_PROVIDER_TIMEOUT do?
Each planning or summary call to one provider has a time limit, ACTION_PROVIDER_TIMEOUT (default 45 seconds; 0 turns it off). After the limit the call moves straight to the next provider (#1474). In the authors' test, a Gemini overload ("503 high demand") made one delegation take almost 12 minutes, while the next provider answered in about 5 seconds.
What should I know before upgrading?
- No schema change and no setting you must set. File writing, deleting and sub-agents stay off.
- An abandoned provider call may keep running in the background until the provider's library returns. Its answer is ignored.
What is not tested yet?
A real provider outage, and a real-model sub-agent run after these two fixes. Sub-agents remain off by default.
More: our release page and the roadmap.
Quick answers
What is ACTION_PROVIDER_TIMEOUT in RagLeap?
A time limit for each planning or summary call to one LLM provider. The default is 45 seconds, and 0 turns it off. After the limit the call moves straight to the next provider.
Are RagLeap sub-agents ready for production?
RagLeap does not present them that way. They are off by default. v0.13.6 fixes two bugs found by their first real-model test, and a re-test after the fixes is not done yet.
What happens when a sub-agent needs no tool?
Since v0.13.6 the child answers the task itself with one short model call and returns that answer to the parent. Before, it returned only 0 step(s): no actions, and the parent delegated the same task again.