Skip to content

dashboard@0.143.0

Choose a tag to compare

@gram-bot gram-bot released this 28 Oct 17:47
· 851 commits to main since this release
b7e13ce

Minor Changes

  • b253145: When choosing how a new agent signs in, an API key stays the default, and the platforms Speakeasy already trusts, such as Claude Tag, now appear beside it as presets that need no key. A custom OIDC issuer moved under an Advanced section on the same step.

  • 1085b08: Agent identities can use personal OAuth connections assigned by their owner or another authorized editor. Editors can attach only their own connections, remove another member's assignment, and explicitly replace it with their own. MCP client authorization alone does not grant permission to change connections.

    Servers appear in one list ordered by recent tool activity, with shared access labeled separately. Assigned connections show whose account is used. All servers preserves valid assignments and names servers without an available connection. Expired assignments are flagged in the agents list and overview and can be refreshed by their account holder. Agent gateways resolve each server's assigned connection when executing tools.

  • 0620b1a: MCP server settings now list the upstream credentials Speakeasy uses to reach the upstream: which kind each is, whether it is on, and which other servers share it. Admins can say whether the upstream needs credentials at all, turn a credential on or off, remove it from one server, and choose who can use it with Can use and Blocked rules that apply wherever the credential is used. Roles can allow or block each kind of upstream credential, and API keys show and edit the servers and credentials they may use.

  • 276e173: GKE is now a workload identity option when creating an agent. The setup trusts one cluster by its project, location and name, admits one namespace and service account on it, and gives the pod manifest and token exchange the workload needs, with no secret stored in the cluster.

  • 10daa1a: Remote session clients on an organization's authorization server can be duplicated from the Clients list or the client's detail page. The copy keeps the original's settings and, by default, its client ID and secret, or registers a new client with the authorization server when it supports dynamic registration. A client metadata document client gets its own document. The copy opens for editing right away, and MCP servers keep using the original.

  • a22772c: Administrators can now correct a remote session client's client ID in place instead of deleting and recreating the client. A corrected ID revokes the sessions obtained through the old one, so users reconnect once. Clients can also be given a display name; a client without one is shown by its client ID.

  • b3e6186: A project's first enabled approval policy now gives it an approvals server, the MCP server agents call request_approval on. Speakeasy creates it at <org>-<project>-approvals, adds it to the Default plugin as speakeasy-approvals and republishes the plugin, so agents that use the Default plugin can request approval without extra setup. The server has its own sign-in issuer: developers in Claude Code or Codex sign in with their Speakeasy account and request approval as themselves, while agents with a key keep using the key. A held call names this server's URL. The policy editor says where the server went, the server shows as Built-in on the MCP and plugin pages, and policies and gateways cannot include it, because the gateway serves it before any policy runs.

  • 4cd0996: Discover advertised OAuth registration and Client ID Metadata Document support during staff catalogue review. Preserve bounded public capability evidence in approved promotions and setup-guide requests, and distinguish unknown authentication evidence from manual setup in catalogue APIs.

    Catalog setup badges and filters distinguish automatic, manual, and unknown setup. CIMD-capable entries use the existing automatic OAuth installation flow.

  • e94ce5d: Add Code Mode discovery for MCP gateways. A single execute tool runs ephemeral Python with tool search, schema descriptions and live authorized calls to hosted, remote and tunneled tools. All tools (frozen) and Specific tools reuse the catalogue fixed at consent from a fast cache; All tools (live) refreshes only approved members. Adding a member requires new consent. Settings, consent and Inspect support connection overrides, execution results and nested-call outcomes.

    Organization gateway connections can choose Code Mode on the consent page too, searching and calling approved tools across projects the person can reach.

    Code Mode is off by default and rolled out per organization: Speakeasy staff enable it from the admin dashboard's organization Features page. New selections also require a configured code runtime.

    Assistant runtime discovery skips terminating sandbox pods when selecting a running pod.

  • 85067d5: Choose All tools (live), All tools (frozen), or Specific tools when approving a gateway connection. Frozen and Specific tools stay fixed at consent and are served from a fast cache, so tool access is much faster; live discovery refreshes tools from the approved member servers. Adding a member or connecting a previously unavailable server requires new consent. Calls execute live and re-check access.

    The organization gateway offers the same tool picker, across every project the person can reach.

  • 4be3c1a: MCP gateways are available to every organization: the MCP page lists them and Add a server offers New gateway, without the gram-gateway-endpoints rollout flag.

    Command K lists gateways by name and opens their overview.

  • 34b8d5b: Hosted MCP servers are managed on the MCP server page: Tools, Resources and Prompts tabs, per-tool Team Access, and hosted Settings sections (tool selection mode, environment variables, server instructions, export). Old toolset page links redirect to the matching tab of the hosting server's page. MCP server reads name a toolset's hosting server in the toolset summary.

  • 640af79: Explore has a risk_findings dataset, so widgets and dashboards can count what the risk policies caught: by category, rule, detector, severity, policy, agent, team and person. It answers counts only, never individual findings, and leaves out the matched values and the chats they came from. Like the rest of the risk surfaces it is for organization administrators: describe lists it to them alone, queries, value lists and widget saves refuse anyone else, and a shared widget over it tells other viewers it is for org admins instead of reading as broken. A Speakeasy-built "Security & risk" dashboard shows findings, high and critical findings, people affected, findings over time by category, top rules, and findings by agent, person and policy. The Platform MCP analytics tools follow the same rules.

  • a58d9a3: Explore signal activity over minutes through calendar months, break it down by captured attributes, inspect measured definitions, and export the measurement context. Demo data includes linked conversations, intraday patterns, missing labels, and separate manual runs.

  • 68a05bc: Find signal patterns across conversations with exact session breadth, top-session concentration, separate message/session co-occurrence denominators, and qualified previous-window comparisons. Dashboard and Platform MCP share the same measurements and permission-checked supporting references.

  • 1e93dfa: Send tool approval requests to approvers as Slack DMs. Each approver on the policy, with roles expanded to people, gets a message from the Speakeasy app with the tool, the agent's reason, each redacted argument as its own field and Approve once and Deny buttons. A click goes through the same approver check as the dashboard, and every DM shows the outcome once the request is decided or expires. New Slack installs ask for chat:write; workspaces installed before it report it under missing_scopes, and the Slack workspaces page asks admins to reinstall. Approvers can always decide in Speakeasy. mise run zero:slack connects a Slack test app to the local organization. Behind the risk-tool-approvals flag.

  • 1570489: Add tool approvals to Guardrails: a "Require approval for tool calls" use case with its own Tools, Who and Review steps (approvers are specific people or roles), a Require approval badge with the approver count in the policy list, and a Tool approvals tab where approvers see held calls with each argument on its own row and the agent's reason, and approve once or deny. The demo org seeds an approval policy with pending, used, denied and expired requests. Behind the risk-tool-approvals flag.

  • 5191698: Tool logs now show who an agent acted for. An agent call made on a person's behalf reads "agent ↳ on behalf of ", and filtering by that person includes the agent calls made for them. The new agent_ids filter narrows those to one agent. Calls recorded before this change show the agent alone.

Patch Changes

  • 1f3a9b8: When a CLI or hooks sign-in link names an organization the user belongs to but is not currently using, the dashboard now switches to that organization and finishes the sign-in. The error page only appears when the account is not a member of that organization.

  • 4ac5c1a: "All servers" in the new agent identity flow, and when editing an agent's servers, no longer ends in "requested agent access exceeds your permissions". The option is offered only when you, and the agent's owner, can reach every server in the agent's project. Otherwise it stays off and says why, and you choose the servers one by one. A server you can see but cannot connect to is marked the same way, and "Select shown" leaves it out. The new agents.checkPolicyGrants endpoint answers whether policy grants could be written, using the same rule as agents.create and agents.createPolicyGrant, and writes nothing.

  • 08b63be: An agent's owner can now see the sessions their agent produced. Without chat:read, Agent Sessions lists your own sessions plus those of agents you own, and you can open them, but deleting one still needs chat:write. chat.list accepts an agent_id filter. The agent page's Overview and Sessions tabs list the agent's recent sessions and link to Agent Sessions filtered to that agent. The list of clients signed in as the agent is now labelled MCP connections.

  • 726bab9: The Agent Sessions detail panel now names the agent that ran a session sent with an agent API key, in its header and in Session details, the same way the session list does. It names a person as "on behalf of" only when the session reports one, and user messages in a session with no person read "User" instead of "anonymous".

  • 0908c44: Organizations can now be granted the default auth permissions the mandatory auth client check needs: everyone's and each agent's use of their own personal connections, shared clients for whoever can connect to a server using them, and a policy for each legacy API key that has none. An offline backfill grants them for every organization and records each grant it writes, so a rerun never restores one an admin removed; the upstream OAuth migration grants them for the clients it records, and new organizations start with the personal default. Role permission counts no longer include these provisioned permissions.

  • 555b83e: Organization admins can decide who may use each auth client: Use grants permission to use the client and Blocked takes it away, on every server that offers the client. Rules on personal clients never let anyone use another person's connection. Admins can also replace an existing API key's own policy with keys.updatePolicy, and a key's policy can only name auth clients and projects in its own organization. Both changes are recorded in the audit log.

  • 6b409a8: Organization admins can list the auth clients Speakeasy uses to reach upstream MCP servers, see which servers offer each one, rename, enable or disable a client, and stop a server offering it. Each server now states whether its upstream needs authentication, so a server that needs it but offers no enabled client reads as incomplete setup rather than as needing none. Stored header values are never returned, and every change is recorded in the audit log.

  • c1a55fb: People can block one agent from their own upstream connection without managing the agent, and agent managers can add auth client restrictions to an agent's policy. Only the person who set a connection block can remove it.

  • c1a55fb: Auth client grants can name an upstream OAuth client with upstream_client, so one restriction covers a person's connection across every auth client that shares it.

  • a85e73d: The Playground and the MCP tool listing now connect to MCP servers that reject the 2026-07-28 protocol version. When a server answers protocol discovery with an unsupported protocol version error, the dashboard retries with the initialize handshake on an older version instead of failing to list tools. Servers that accept 2026-07-28 keep using it.

  • cbea82c: Hosted MCP server settings list every address and offer to add or remove them, including another Speakeasy-hosted address. Removing the last address of an enabled hosted server asks you to disable it first.

  • 593b110: Hosted MCP server settings now save the slug, custom domain, network access and the linked sign-in issuer through the MCP server and endpoint APIs instead of the deprecated toolset hosting endpoints, and slug checks use the endpoint slug availability check. Toolsets without a hosted MCP server still link their issuer through the toolset. After a save that changes the server's slug, the page now moves to the new address instead of showing "not found".

  • cbea82c: The MCP address availability check takes an optional mcp_server_id, so a server adding its own older address in Settings no longer sees it as already taken.

  • cbea82c: Hosted MCP server settings show the older Speakeasy-hosted address a custom-domain address still serves, instead of saying there is no hosted address.

  • 177fcd9: Observability filters select hosted MCP servers by server id. Links that still carry a toolset slug keep working. The MCP server overview now lists top users for every hosted server.

  • ceb2d8f: Plugin servers are always backed by an MCP server or a gateway now, so the unresolved plugin server backend is gone from get_plugin and the plugin page shows gateway members as "Gateway" instead of "Toolset missing".

  • 0bc2702: Show actionable error pages for expired sign-in and setup callbacks. Link setup failures directly back to organization setup, dashboard connection failures back to the dashboard, and assistant failures back to the conversation or assistant. Return canceled sign-ins to consent or login, and explain how to restart failed assistant connections.

  • dc16595: Okta connections accept org URLs on okta-gov.com (Okta for Government High) and trexcloud.com (the orgs Okta uses to review integration submissions).

  • 5297c22: People can hide gateway MCP servers they do not use. Hidden servers leave the gateway's tools, list last on the consent page with a Show button, and are readable and settable through the hiddenMcpServers API.

  • a6c7113: The gateway Tool discovery setting explains that Code Mode is not enabled for the organization in a tooltip on the disabled Code Mode option, instead of a note that always shows under the field.

  • 2fecbce: The Device Agent macOS install command downloads the pkg from the Speakeasy server's stable link, so a copied command always installs the current version, and a failed version lookup offers that link instead of manual steps.

  • a232676: Add a shared Connections view for project and Organization Gateways, with organization-wide upstream visibility, identity search, server/provider association filters, creation dates, and authorization ordering. Apply filters before cursor pagination and support loading subsequent pages and retrying errors on gateway and provider-client session lists. Expose upstream authorization deadlines separately from access-token and refresh-token expiry.

    Add administrator session inspection through Platform MCP and Command K navigation to gateway connections and client registrations. Refresh relative date filters and include entire selected calendar days.

  • fbe8a8c: A gateway connection approved with "Gateway default" now keeps the discovery mode that was the default at consent until it reconnects, so changing a gateway's default mode (for example to Code Mode) no longer swaps the tools of connected clients mid-session. A tool call for a tool the connection's mode does not serve now says the gateway's tools may have changed and to reconnect, instead of "unknown code mode tool".

  • c060f27: The GKE workload identity setup in the agent wizard now shows the audience, token endpoint and MCP server URL a workload needs as labeled, copyable values, and says which placeholders remain when Speakeasy cannot fill them in. Its example call targets one of the agent's own servers, served over HTTPS, instead of a placeholder URL.

  • 1a78d88: Use valid table rows and cells for expandable content while preserving expansion and collapse behavior.

  • 20eabcd: Hosted MCP servers now edit their address in the same endpoints table as other servers. A hosted server keeps one address, so settings no longer offer to add or remove one, except to add an address to a server that lost its own. The address moves onto the verified custom domain in place, and back to the Speakeasy domain once that domain can no longer serve.

  • 3412532: MCP server pages now live at /mcp/<server>/<tab>. Older links keep working: /mcp/x/<server>/... redirects to the new address, and /mcp/<toolset>/... opens the page of the server that hosts the toolset. When a server and a toolset share a slug, the server wins.

  • d586069: The Platform MCP setup-guide search tool is now search_speakeasy_docs (was search_gram_docs), and setup guide resources use speakeasy://platform-mcp/setup/... URIs instead of gram://. Hosts that see only the Platform MCP discovery tools are now told to answer how-to and setup questions with search_speakeasy_docs and cite the pages it returns.

  • 628e396: Agent identity pages now work while a platform admin has the RBAC override turned on. Agent management no longer rejects requests that carry the override. Instead, the override narrows each agent permission check: the check must pass both your real grants and the override. Registered agents remain visible in the roster and Command K, with their available actions refreshed when the override changes. Agent owners keep managing their own agents, and delegating access to an agent is still limited by your real grants.

  • 1ca6078: Add risk.listApprovals, risk.getApproval and risk.decideApproval for tool approval requests. Org admins see every request; other members see the requests they can approve and their own. Only a listed approver, signed in to the dashboard, may decide, and never the person who made the call. Requests and decisions are recorded in the audit log, and creating approval policies is gated behind the risk-tool-approvals flag.

  • 36ccde6: Add the require_approval risk policy action for MCP tool calls. A covered call is held and returns a request token; the agent files the request with request_approval on the new Speakeasy Approvals MCP server, waits with the watcher it returns, and retries once an approver approves. Each approval releases exactly one retry of the same call. The dashboard shows approval policies read-only until their editor ships.

  • ff6a2b2: Removing an "All" permission from a role now also removes unrestricted grants stored by older versions, which previously stayed in place. The role editor now checks the permissions the server saved and shows an error, keeping Save enabled, instead of reporting "Role saved" when a permission change did not persist.

  • f28c59d: Filter Tool Logs by agent identity, alone or together with a user to see the calls an agent made on that person's behalf. The old Agent facet is now Harness, the User column is now Identity, the facet rail is narrower, and the assistant dock no longer covers the table. Agent and person names in "on behalf of" lines underline on hover.

  • 31bd957: Tool Logs filter counts now narrow as you filter: each filter group lists only the values that still have calls under the other applied filters, while its own values stay selectable. The time range moves next to the search bar, and the summary and timeline panel takes less vertical space.

  • 000bc5d: The overview of an unproxied MCP server no longer shows a visibility setting. Clients connect to these servers at the vendor's own URL, so the setting had no effect.

  • 863893f: Add workload identity setup for inference. Workloads can exchange trusted issuer JWTs for project-bound inference tokens when their assigned agent and owner explicitly have inference permission, without MCP configuration or transcript access.