backstage release v3.8.0
Added
- (agent-platform) Classify failed sessions and add the notification row rule by @marians — Groundwork for the notification bell below: the portal now tells why a failed session failed (model unavailable, a tool failed, runtime lost or other) without passing on the failure’s text, and decides which sessions get a notification.
- (agent-platform) Set a session’s notification level from its menu by @marians — A session’s ⋯ menu, on its page and in the Sessions list, has a
Notificationssubmenu withDefault,All activityandMuted. The notification bell follows it: All activity adds finished turns, Muted leaves the session out. - (agent-platform, muster) Name the installation on every connector, tool and workflow link by @marians — The command palette lists a connector once per environment it is registered on, each opening the connector in that environment, instead of one row for all of them.
- (agent-platform, muster) Move the Agent Platform to URLs that follow the rail by @marians — Agent Platform pages move to shorter addresses:
/sessions,/usage,/profile, and every agent, skill, connector, model and workflow page under its Customize tab. Old links and bookmarks land on the same page. For operators:app.extensionsentries namingpage:agent-platform/skills,sub-page:agent-platform/sessions,sub-page:agent-platform/usageorpage:muster/mcp-servers-redirectno longer apply. - (app, agent-platform, ui-react) Add the Notification inbox to the Agent Platform shell by @marians — A bell on the rail’s Profile row counts and lists the sessions waiting for you, failed, or finished a turn (at
All activity), withMark all readand aDesktop notificationsswitch. The tab title shows the unread count; on a phone the list is in the Profile menu. - (muster) Keep the typed connector name as its display name by @marians — A connector added under Customize’s Connectors keeps the name you typed, e.g.
Stack Overflow, as the name shown everywhere, and Edit can rename it; its technical name stays. Needs muster 5.43.0 or later; an older muster registers connectors as before.
Fixed
- (agent-platform) Show a failed agent read as an error with Retry, not as no agents by @teemow — When reading your agents fails, or an outdated cached list is restored, the Agent Platform home no longer offers to create a first agent: it shows
Couldn't load your agentswithRetry, andNo agents yetonly after a read that found none. - (agent-platform) Show an error when an answer cannot resume the session by @marians — Answering an agent’s question in a session kagent can no longer resume shows
Could not resume this sessioninstead of silently doing nothing, and offers a new session that starts with the conversation so far and your answer. - (agent-platform) Carry the whole conversation into a lost runtime’s new session by @marians — When a session’s runtime is lost, its notice has a
Continue in a new sessionbutton that starts a new session with the whole conversation and aContinued sessionbanner linking back. A session that cannot continue no longer shows a message box. - (muster) Make the Reads and Changes things badges legible by @marians — On a connector’s tool list, tool and workflow pages, the agent tool catalogue and the approval card, the
ReadsandChanges thingslabels are 12px instead of 10px, andReadshas a light grey background instead of showing as bare text.
Full Changelog: https://github.com/giantswarm/backstage/compare/v3.7.1...v3.8.0