See what you have connected, and disconnect it

Connected apps used to render a catalog of the two systems we had written code for. Your actual connections showed as not connected, and there was no way to disconnect anything at all. The platform could refuse an operation with "disconnect it first" while offering nowhere to do that.

The console now lists your real connections with their status, and a Disconnect button. Disconnecting is a status change rather than a delete, so it takes effect everywhere at once and keeps the audit trail, and connecting the same system again brings the row back rather than colliding with it.

The catalog is gone in the other direction too. You are not limited to systems we shipped code for: name whatever your workflow needs, connect it during the interview, and publish is what insists a named system is actually connected. The interview stopped telling anyone a system is unsupported, because with authored integrations there is no list for a name to be missing from.

The Add-trigger dialog over those same two systems has been removed. It returned a success toast and wrote a trigger row that could never fire.

Signing in to a third-party site through the agent's browser works now. Starting a hosted login takes two calls to our browser provider and we were only making the first, so every login card rendered without a link to open. Both calls happen, a repeat login picks up the existing connection instead of failing, and the pages you land on when the login finishes exist.