I think LLM calls may be broken as of recently :th...
# proj-agent-canvas
q
I think LLM calls may be broken as of recently 🧵
You are getting this because the latest local Agent Canvas code is launching an
agent-server
dependency set that can resolve to an incompatible LiteLLM/MCP combination. I checked the repo and the current code path is: • pins Agent Server to
1.55.1
. • launches it through
uvx
. •
openhands-sdk==1.55.1
depends on: ◦
litellm>=1.93.0
with no upper bound ◦
fastmcp<4,>=3.2.0
•
fastmcp
pulls
mcp<2.0
, currently resolving to
mcp==1.30.0
. • Because LiteLLM has no upper bound in SDK
1.55.1
,
uv
resolves
litellm==1.106.0
. That combination is broken:
Copy code
litellm==1.106.0 imports CacheableResult from mcp.types
mcp==1.30.0 does not define CacheableResult
So when an LLM call goes through LiteLLM, LiteLLM imports its MCP/proxy code and fails here:
Copy code
cannot import name 'CacheableResult' from 'mcp.types'
The error is then wrapped as:
Copy code
LLMServiceUnavailableError
  litellm.APIConnectionError
    Litellm_proxyException
Recommended fixes: 1. upgrading the Agent Server stack to `1.56.0`: 2. Pin LiteLLM below
1.106
in the agent-server environment:
Copy code
litellm<1.106
l
Yeah, 1.56.0 fixes this, trying to get a release out
ty 1
BTW @quick-window-91705 do you think we could remove the limit that branches need to be up to date before merge on OpenHands/automation? It’s making it very slow to get the release out there
q
Yep we should remove it
Removed it
🙏 1
e
Was here to report this
l
preaparing a canvas release now
🙏 1
q
1.28.1 release is out
🙌 5
i
@refined-judge-86309 this might have been your issue.