On October 20 the routing-rule list gained a second presentation, and connector credentials got a stricter rule.
Routing rules: table or cards
The routing-rule list now offers table and card views, chosen at the top right. Cards are laid out in routing order; the number at a card's top right turns into a drag handle on hover, and dropping it on another card reorders the rules exactly like dragging the order column in the table. Each card keeps its more actions (⋯) menu. In the card view, the View menu gains a Last modified switch that hides that line at the bottom of each card. The choice is remembered per member: reloading the page, opening another tab, or switching to another collaboration space shows the view you picked last.
A changed destination leaves the old credentials behind
The people who can edit an MCP server or an A2A agent are not necessarily the people who enter its credentials, so a credential only holds for the destination it was entered for. Changing an MCP server's transport / command / args / URL, or an A2A agent's Card URL, moves the destination: every shared secret already stored in the config must be typed again in the same edit, or the save fails and lists the keys to re-enter. Every member's per-user credential is revoked at the same time, so each member enters their key again or authorizes again against the new destination. Replacing only the OAuth metadata revokes members' per-user credentials alone.
Protected values no longer show their first and last characters
Protected values in lists and detail pages now read as a plain ****. A member who can view but not edit also loses the MCP args, and sees the credentials and every query value in a URL masked.
Get started
Routing rules live on a collaboration space's Routing rules page. MCP servers and A2A agents live under Flashduty console → AI SRE → Customize.
Product docs: Routing rules, MCP, Agent.