<https://github.com/OpenHands/OpenHands/pull/14182...
# proj-agent-canvas
q
https://github.com/OpenHands/OpenHands/pull/14182 - rest API to send a message to a running conversation
✅ 1
cc @fierce-account-55183 maybe
👀 1
f
Is this for use in integrations? Or is it designed to make using the conversation api simpler? The original intention for cases like this is you would ask the app server about a conversation using
/api/v1/app-conversations
, and it would tell you where it is running using the
conversation_url
and then you could simply send the message directly to that agent server instance. I suppose that process is a little bit complex, but it does keep it very clear what is going on and where. On the other hand, this is simpler to use but could make it more confusing about what is going on. There is a community PR which I was going to help with this week about proxying websocket connections through the app server (Depending on an environment variable flag) which is similar in purpose to this.
q
See this: https://linear.app/all-hands-ai/issue/APP-781/ohe-rest-api-to-submit-follow-up-messages-to-an-existing-conversation It's meant to make manipulating convos simpler via just REST APIs, instead of having to interact via websocket
f
I guess the details are slightly incorrect - you don't need a websocket as is - you can use the rest endpoints on the agent server. But it does show that community members are finding it difficult to grok the current approach.
nod 1
q
Yeah was just abt to say that ^
f
I'll approve on that basis
ty 1
I've requested 2 documentation changes - LMK once those are in and you have my full approval
ty 1
🍰