Overwrite the default 60s timeout limit for tool use

[Steven Pham]

Hi,

I've beening using RovoDev Beta for the last 2 months, this timeout limit appears to be a recent update.

I have a few custom MCPs that RovoDev is instructed to use whenever there are needs for deep codebase analyses, which often requires a long wait time to complete, and this limit so far has been quite a road block where the tool call stops mid way after waiting and RovoDev moves on with the task without the sufficient context from the MCPs' results.

Hope the team can help addressing this, or other super users can advise a quick mitigation tip if it is possible.

Thanks,

Pham

[Dr Valeri Colon _Connect Centric_]

@Steven Pham The 60-second tool timeout is hard-coded in the current Rovo Dev CLI, and you can’t override it. Long-running MCP tools will always be cut off and the LLM will continue without the results. The only workaround is making the MCP return partial/streamed output quickly or splitting the analysis into shorter steps. Atlassian is aware and evaluating longer or configurable timeouts.