I'm running into a new issue that seems to come from something upstream. Summary from agent investigation since I am out of my comfort zone with python compat and dependency: > We hit a packaging compatibility issue, not an agent-server runtime regression. Agent Canvas launches agent-server via

uvx

, which creates an unpinned Python environment outside npm’s lockfile. SDK 1.35 allows

litellm>=1.84.1

, so the resolver selected LiteLLM 1.92.0 on a host where uv chose Python 3.14. LiteLLM 1.92.0 still declares Python

<3.14

, but its new Rust/Maturin build path invokes PyO3 0.23.5 and fails before that incompatibility is handled cleanly. Pinning agent-server’s uvx environment to Python 3.13 fixes startup. Longer-term, SDK should advertise

<3.14

until its full dependency graph supports 3.14, and Canvas should explicitly request Python 3.13 as a guardrail. I did an

npm ci

locally and just updated my personal machine to canvas 1.30 and neither can start the agent server now

I went into the rabbit hole on the litellm side. They have a whole pile of PRs from people tryin' to fix. Pinning to 3.13 looks to me like the only sane option atm.

Unfortunate. I'm surprised no one else has run in to this. Without the PR on top of canvas I can't even start it. I need to switch to that branch just to run canvas right now

On the litellm side, I found a PR that was nothing but the version bump. It was a month old. Then I saw somebody else who had the same version bump but there was a lot more work in that one, And I saw some others that looked like they were likely attempts at unclogging the same issue. That's where I checked out. They don't need my voice in that mob.

i’m taking a look at this!