Ada CLI 1.3.0
This release lets you pin a custom metric to a change set.
Changes
This section lists what the release adds or changes.
custom-metrics createtakes--changeset <id>. It pins the new metric to a change set that is still in testing. The metric is deleted when the change set is promoted, deleted or expires. The pin cannot change after create. For example:adacli <instance> custom-metrics create --name "Refund date given" --pass-description "..." --fail-description "..." --scoring-guidance "..." --subject ai_agent --changeset <changeset-id>.custom-metrics getshows aPinned To Change Setrow for a pinned metric.
See Ada CLI.
MCP server: tool permissions for members and API keys
Owners can control which MCP tools connected assistants can use from Config > PLATFORM > MCP server. The server enforces these permissions in every MCP client.
What Owners can set
Global settings limit tools for everyone, including Owners and API keys. With individual settings, an Owner can also give specific team members or API keys fewer tools. An Owner can change many members or keys at once and choose starting tools for new members.
Effect on existing access
Existing connections keep their access until an Owner saves restrictions. When an Owner first enables individual settings, existing members and API keys keep their tools. With individual settings enabled, a new API key has no MCP tools until an Owner allows them.
See Tool permissions for setup and limits.
Messaging embed shim installs with no dependencies
The @ada-cx/messaging-embed npm package now has no dependencies. Installing it no longer installs @ada-cx/messaging-sdk, and its TypeScript types ship inside the package.
Sites whose security review allows no Ada loader in their dependency tree can install the shim on its own. The shim’s behavior does not change.
See Iframe-only embed for setup.
Ask steps can hide the keyboard input while quick replies show
A Playbooks ASK step that shows its accepted values as quick replies can now hide the message box while the options show, so the end user must tap one. Enable the Hide keyboard input toggle in the step’s Messaging channel settings. The toggle is available when Quick replies is selected for the step, and it is disabled by default.
The setting applies on the Web Chat widget and the messaging SDK. On other channels the message box stays available. See Quick replies for accepted values.
Dashboard sign-ins now appear in the Audit log
The Audit log now records when a team member signs in to the dashboard, fails to sign in, or signs out. Security and compliance reviews can use these entries to show who accessed your AI Agent and when.
Each entry shows the team member, the sign-in method, such as Password, SSO, or Dialpad, and the interface. A failed sign-in is recorded only when the email belongs to a team member. Only Owners and Administrators see Sign-in entries on the Audit log page, in its filters and in the CSV export. Entries start on November 4, 2026. Earlier sign-ins are not recorded.
The entries also appear in the CSV export, the Audit log API, and the v1.audit_log.emitted webhook.
Learn more about the Audit log.