Ada CLI 1.6.0
This release lets you set the reasoning level of staged playbooks, and warns you when a staged playbook would lower a step from High reasoning to Normal.
Changes
This section lists what the release adds or changes.
changesets stagetakes--reasoning-level <high|normal>. It sets the reasoning level on every set and ask step in the staged playbooks, and overrides the levels in the file. For example:adacli <instance> changesets stage --name "Orders on High" --file changes.json --reasoning-level high.changesets stagewarns when a staged playbook would change a step from High reasoning to Normal. The warning names each step. The change still stages.
See Ada CLI.
Ada CLI 1.7.0
This release warns before testing runs create starts a batch that may not fit in the daily test run quota.
Changes
This section lists what the release adds or changes.
testing runs createreads the daily test run quota before the first run starts. A batch is the number of unique test case IDs times--repeat. If the batch is larger than the runs left today, the command prints a warning on stderr: the batch may not fit, and some runs can start before the api refuses the rest. The command then starts the runs, and the api decides. The exit code and the--jsonoutput do not change.testing runs create --no-quota-checkstarts the runs without a read of the quota. For example:adacli <instance> testing runs create --cases <id> --repeat 3 --no-quota-check.testing quotaandtesting runs createprint a warning when the daily limit is far below the default of 3,000 runs. Contact Ada support if you see it.
The quota can show fewer runs left than the api allows. For example, it counts cancelled runs, and the api does not enforce the limit on a non-production instance. So the warning can show for a batch that fits.
See Ada CLI.
Ada CLI 1.8.0
This release makes playbooks create create an inactive playbook unless you pass --active.
Changes
This section lists what the release adds or changes.
playbooks createmakes an inactive playbook by default. An inactive playbook does not run in conversations with end users. Before this release, a playbook created with no state option was active at once. If a script relies on that, add--activeto the command.playbooks create --inactivestates the default. For example:adacli <instance> playbooks create --name "Returns" --file steps.json --inactive.--activeand--inactivecannot be combined.- When the new playbook is inactive, the command prints how to make it live:
playbooks update <id> --active.
See Ada CLI.
Ada CLI 1.9.0
This release adds commands that test a changeset against the live AI agent. They show only on an AI agent that has the improvement loop turned on.
Changes
This section lists what the release adds or changes.
changesets test start <changeset_id> --metric <id>runs each test case that lists the metric on the changeset and on the live AI agent. The metric is the objective of the changeset or a custom metric.--repeatssets the runs of each test case on each side, from 1 to 5. The default is 3. The runs use Ada’s improvement quota, not the simulation quota. For example:adacli <instance> changesets test start <changeset_id> --metric <id>.changesets test get <test_id>shows the result: the outcome of each test case on each side, and the test cases that the changeset fixed and broke. For example:adacli <instance> changesets test get <test_id>.
See Ada CLI.
MCP server: connect Microsoft Copilot without a packaged agent
You can now connect Microsoft Copilot to the MCP server yourself. Build a Copilot agent in Microsoft Copilot Studio, and add the MCP server with your OAuth connection URL. People then use the Copilot agent in Microsoft 365 Copilot and Microsoft Teams.
Previously, Ada packaged a Copilot agent for each AI Agent, and an IT admin imported the package into Copilot Studio. You no longer need the package. Copilot agents imported from a package continue to work. An admin is necessary only to make the Copilot agent available to the whole organization.
Learn more in the Microsoft Copilot documentation.
Mobile SDK branding and web settings
The iOS, Android, and React Native Messaging SDKs now accept branding to override dashboard appearance for each SDK instance.
An app can set its own AI Agent name, avatar, colors, and text size with the same fields as the web SDK.
Fields that you omit keep their dashboard values. Overrides stay in effect after a chat reset and document reload.
Branding does not add to the WebView URL length. Malformed input is ignored and reported once per document without its value.
Host overrides, including launcher text and icon URLs, are not saved in the startup cache.
The SDKs also accept testMode, skipGreeting, start theme, locale, appUrlFallback, and showFallbackOnTimeout.
Apps can record business events with trackEvent, change the formatting locale with setLanguage, and reset with a fresh identity token.
A reset can also skip its next greeting. Existing calls and defaults stay unchanged. These additions apply only to Messaging.
Use iOS 1.7.0, Android 1.7.0, or React Native 1.6.0 with the Messaging runtime. See the iOS, Android, and React Native references.
Exclude pages from a web import
You can now leave pages out of a web import that crawls an entire website. Under Every webpage starting from one URL, add the paths to skip in Exclude pages, separated by commas. A path such as /blog excludes that page and every page under it, and * matches any text.
Set the list when you add a website, or change it later from the source’s Settings on the Sources tab. A change applies from the next sync. Articles already imported from a page you exclude stay in your knowledge until you delete them or set them to Inactive.
For more information, see Web import.