Add Title Generation LLM Profile in `Application`...
# proj-agent-canvas
s
Add Title Generation LLM Profile in
Application
setting. (good for using small model + ACP conversations can have titles. Also customers have been asking for it) • Canvas: github.com/OpenHands/agent-canvas/pull/1910 • OpenHands SaaS/Enterprise: github.com/OpenHands/OpenHands/pull/15366
šŸ™Œ 1
Canvas
Copy code
Adds a "Conversation titles" setting under App Settings, with the same UX for local Canvas, SaaS, and Enterprise. Users can select any available LLM profile or choose "Automatic." We placed it in App Settings because it is a user preference,
  while the LLM Profiles page remains focused on creating and managing profiles. Local Canvas stores it as an app preference; cloud sends it to the OpenHands backend.
OpenHands Enterprise
Copy code
Adds backend support for resolving the selected title profile and passing it to both OpenHands and ACP conversations. In Enterprise, the preference is stored per organization membership because the available profiles are organization-scoped.
  Owners/admins manage the organization's profile catalog and default, while regular members may select from that approved catalog for themselves. "Automatic" uses the organization's active profile, then falls back to the agent LLM. Rename and
  delete operations reconcile affected member preferences safely.
thanks on a stick 1
• bump can I get šŸ‘€ on Canvas: github.com/OpenHands/agent-canvas/pull/1910 • OpenHands SaaS/Enterprise: github.com/OpenHands/OpenHands/pull/15366 ?
āœ… 1
c
I was so concerned about resolving the entire profile client-side that when I saw it once, I assumed it was used everywhere. My bad! Both look good
s
its also possible to do the fallback in the agent-server https://github.com/OpenHands/software-agent-sdk/pull/4215
not sure if cleaner tbh
c
Maybe like
/profiles/
(or
/llm_profiles
) is CRUD => we can read e.g.
GET /profiles/name
? the client saves name as title profile, and asks for name šŸ¤”