https://docs.all-hands.dev/ logo
Join Slack
Powered by
Hey, I was looking into the `typescript-client` r...
# proj-agent-server
m
Hey, I was looking into the 
typescript-client
recently and noticed some discrepancies: we have client releases with endpoints that are no longer served by the 
agent-server
, as well as server endpoints that aren't yet supported by the 
typescript-client
release. The 
typescript-client
should be a wrapper around the 
agent-server
that provides the exact same functionality. To help with this, I created a small test to audit the two (specifically, it checks the endpoints exposed in the 
agent-server
against the endpoints supported in the 
typescript-client
). (see output in the 🧵 ) -> https://github.com/OpenHands/typescript-client/pull/216 Moreover, to make this test truly useful, we should probably update the release process for TypeScript. Right now, we just tag 
main
and it gets released. I suggest we follow a process closer to what we do in the SDK: • For a release, create a new branch named 
release-TAG
. • Run the above audit tests on this branch (and make them mandatory). • If everything is a 1:1 match, we can tag the branch and release it. PS: In a best-case scenario, we would have automation in place so that every time the 
agent-server
is released, the corresponding PRs to update the 
typescript-client
are automatically opened.
👍 1
✅ 1
⛔ (no known backend) — served by no backend we can see (14) • 
DELETE /api/meta-profiles/{}
• 
GET /api/meta-profiles
• 
GET /api/meta-profiles/{}
• 
GET /api/security/export-trace
• 
GET /api/security/policy
• 
GET /api/security/settings
• 
POST /api/cloud-proxy
• 
POST /api/conversations/{}/generate_title
• 
POST /api/meta-profiles/{}
• 
POST /api/meta-profiles/{}/activate
• 
POST /api/security/policy
• 
POST /api/security/settings
• 
POST /api/skills/installed/{}/update
• 
POST /api/unset-provider-tokens
↗️ served by 
cloud
(5) • 
DELETE /api/keys/{}
• 
GET /api/keys
• 
GET /api/shared-events/search
• 
POST /api/accept_tos
• 
POST /api/keys
➕ Missing API — agent-server exposes it, client does not implement (17) • 
GET /
• 
GET /api/bash/bash_events
• 
GET /api/conversations
• 
GET /api/conversations/{}/events
• 
GET /api/conversations/{}/workspace
• 
GET /api/conversations/{}/workspace/{}
• 
GET /api/init
• 
GET /api/llm/subscription/openai/models
• 
GET /api/llm/subscription/openai/status
• 
POST /api/conversations/{}/goal
• 
POST /api/conversations/{}/goal/resume
• 
POST /api/conversations/{}/goal/stop
• 
POST /api/init
• 
POST /api/llm/subscription/openai/device/poll
• 
POST /api/llm/subscription/openai/device/start
• 
POST /api/llm/subscription/openai/logout
• 
POST /api/skills/installed/{}/refresh
c
We could port prepare-release skill I think
👍 1
2 Views
Open in Slack
PreviousNext
Powered by