I've been working a bunch creating custom UIs arou...
# proj-agent
w
I've been working a bunch creating custom UIs around the SDK, and have found the existing autotitling flow extremely hard to work with. I think the current process requires the frontend to send one POST to generate a title, then a subsequent one to actually change to the new title. This seems to be really hard to make work in practice, and I think it might be triggering some kind of race because frequently the title doesn't update This PR adds a new
autotitle
field to the create conversation endpoint, which default to
True
. https://github.com/OpenHands/software-agent-sdk/pull/2225/changes
c
It would be lovely if we can simplify it that way. (my openhands “restored backwards compatibility” lol, it made a commit restoring the POST, but I would definitely remove that commit) I think maybe @straight-sundown-84319 has some context into why it was needed later?
w
agreed on keeping the old API
s
I think it's a good simplification - we can get away without the old title
c
The app-server counter-part PR of this: https://github.com/OpenHands/OpenHands/pull/13093
The agent tested it and it constantly creates the title on the second user message. We will probably want to fix the order on agent-server so that it fires after the first user message, if possible, capturing the first; currently the callbacks run too early, before the first user message is a saved event, so it works at the time of the second message.