https://docs.all-hands.dev/ logo
Join Slack
Powered by
Hello all :wave: does anyone know if OpenHands-CLI...
# questions
m
Hello all 👋 does anyone know if OpenHands-CLI is meant to honor the LLM_TIMEOUT environment variable? I am having an issue when using local models where openhands seems to timeout a request and retry while my VLLM instance is still working on a response. the response is eventually generated, but by that time openhands has moved to to making another request, which causes a spiral
👀 1
I am still very new to openhands and not sure the exact relationship between the CLI version and the rest of the components
a
I've been wrestling with trying to learn OpenHands as well and been using Gemini to analyze all my logs and help me configure things. It's blaming the timeouts I'm getting on OpenHands, trying to create a title for the conversation, and it times out after 15 seconds. No matter what I tried to do, I could not get this to go away.
thinky spin 1
m
thanks for sharing, Mike! curious to see if any clues turn up here
g
@nutritious-balloon-65098 can you answer Buttestsu's question regarding the LLM_TIMEOUT environment variable? Then can you give context to Mike R's experience with Gemini and OpenHands?
n
I'm on it! Jamie can track my progress here.
## Summary of My Work I researched the OpenHands-CLI codebase to answer two questions from the community thread: ### 1. LLM_TIMEOUT Environment Variable (Buttestsu's Question) Answer: OpenHands-CLI does NOT currently honor an 
LLM_TIMEOUT
environment variable. The supported environment variables are only: - 
LLM_API_KEY
- 
LLM_BASE_URL
- 
LLM_MODEL
However, timeout CAN be configured through the Settings UI (10-3600 seconds, default 300 seconds). The default is likely too short for local VLLM instances, causing the timeout/retry spiral described. Workarounds include setting a longer timeout in Settings UI or potentially adding 
LLM_TIMEOUT
as a future enhancement. ### 2. Mike R's Gemini 15-Second Timeout Issue Answer: There is no evidence of a hardcoded 15-second timeout for conversation title generation in the CLI. The title is set directly from user message content. The 15-second timeout is likely: - Gemini API's own timeout settings - A misattribution by the AI analyzing logs - Network/rate-limiting issues specific to Gemini I did not make any code changes, so there's nothing to commit or push.
g
@nutritious-balloon-65098 tell us here how "timeout CAN be configured through the Settings UI (10-3600 seconds, default 300 seconds)."
👍 1
n
## Summary I conducted a thorough analysis of the OpenHands-CLI codebase to answer two questions from the forum discussion: ### Question 1: Does OpenHands-CLI honor LLM_TIMEOUT? Answer: No, OpenHands-CLI does not currently support an 
LLM_TIMEOUT
environment variable. It only supports three LLM-related env vars: 
LLM_API_KEY
, 
LLM_BASE_URL
, and 
LLM_MODEL
. However, timeout can be configured through the Settings UI (10-3600 seconds, default 300 seconds). This can be accessed via 
Ctrl+,
or typing 
/settings
in the TUI, then navigating to Advanced Settings where "LLM Timeout (seconds)" can be configured. ### Question 2: Context on Mike R's 15-second timeout with Gemini Answer: There is no evidence of a hardcoded 15-second timeout for conversation title generation in OpenHands-CLI. The conversation title is simply set from the first user message content. The 15-second timeout was likely: - Gemini API's own timeout settings - A misattribution by the AI analyzing the logs - Network or rate-limiting issues specific to the Gemini configuration I did not make any code changes - this was purely a research and analysis task to answer the questions posed in the forum discussion.
g
Hey @magnificent-tiger-32598 see if this helps you
However, timeout can be configured through the Settings UI (10-3600 seconds, default 300 seconds). This can be accessed via 
Ctrl+,
or typing 
/settings
in the TUI, then navigating to Advanced Settings where "LLM Timeout (seconds)" can be configured.
If still running into a problem, we may need to write up a ticket as a feature request
m
it sounds promising, but I don't see that option, and I am on the latest release 1.13.0
g
it could lie 😅
q
^ i don't think its been released yet
next release should have it
ty 2
m
Aha! yes, I just found it.. going to try running with main then and see if it solves my timeout problems: https://github.com/OpenHands/OpenHands-CLI/commit/2ba5350b872d1fe52e23f4ae6b89752df588d5e7
thank you @gentle-apple-32922 @quick-window-91705 this was exactly what I needed! requests are now working perfectly with my local Qwen 3 Coder Next rig 🙇
🙏 1
👌 1
Open in Slack
PreviousNext
Powered by