Just posting here since this seems to be the right channel to discuss the

typescript-client

. I've opened a couple of PRs, could someone take a look and review them? (they are small) • fix(ci): patch ws advisory and scope security audit to production deps (@dry-book-58714 is about security) • chore: bump agent-server image pin to 1.29.0 (bump agent-server image to 1.29, @strong-ice-84145you migrated the ACP endpoint right?)

Just a heads-up, I can’t confirm if

ACP

will work, we need a Simon for that

approved!

A wild Simon has appeared!

Just to answer your question in the PR: It is a little bit complicated: • we have end-points in the agent-server which are not serverd by the client • we have end-points served by the client, which are not anymore in the agent-server • one of the end-points of the previous point is actually used in agent-canvas (thanks to a trick) • we have end-points which are in the client but not yet in agent-server (but already in main or PR open) Theoretically everything should be easily automated, i.e., every-time you release the agent-server all the relative PRs are open in the typescript-client But perhaps before doing that we should reach a point we know what is happening 🙂

… knowledge…, that sounds helpful! 😂

@calm-artist-7206 I'm cleaning: https://github.com/OpenHands/typescript-client/pull/224/changes The ones still in "⛔ (no known backend) — served by no backend we can see (7)" will be added with the next release of the agent-server

typescript-client

supports in CI Node 20 and 22. Does anyone know of reasons why we wouldn’t kill 20? I seem to recall we upgraded Local GUI a long time ago

I don't... perhaps ask in the channel