> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/releasenotes/release-notes/agent-studio-release-notes.md).

# Agent Studio: Release notes

{% updates format="full" %}
{% update date="2026-10-09" %}

## Highlights

* **Clearer production deployment for tools with multiple integrations -** Easily identify the required integrations during deployment, reducing confusion and preventing incorrect selections.
* **Bug Fixes** - Prevent duplicate tickets in Regression Datasets, Persist input schema updates.

## New features

<details>

<summary><strong>Clearer production deployment for tools with multiple integrations</strong></summary>

The production deployment experience is now clearer when a tool includes multiple API task integrations.

**Customer benefit:** Users can identify the required integrations more easily during deployment, reducing confusion and helping prevent incorrect selections.

**What changed**

* Improved the deployment interface for tools that use multiple integrations.
* Displayed shared tool integrations only once during import and production deployment.
* Verified the updated behavior in Concept, Preprod, QA, and production environments.

<figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2FKOwnQkNiHTZCzYndRo9i%2Fimage-20261006-060808-20261009-083641.png?alt=media&amp;token=ffd88f24-bd42-45bc-b6a6-eb75f67830cb" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Prevent duplicate tickets in Regression Datasets</strong></summary>

Fixed an issue that could add the same ticket ID to a Regression Dataset multiple times.

**Customer benefit:** Regression Datasets remain accurate and easier to manage, with each ticket represented only once.

**What changed**

* Prevented duplicate additions of the same ticket ID to a Regression Dataset.
* Preserved existing dataset contents while preventing repeated entries.

</details>

<details>

<summary><strong>Persist input schema updates</strong></summary>

Fixed an issue where changes made to a tool’s JSON input schema in the Advanced Panel were not retained after saving and refreshing.

**Customer benefit:** Tool designers can update input schemas with confidence, and test executions use the saved schema instead of reverting to an earlier version.

**What changed**

* Ensured JSON schema changes persist after saving a draft.
* Retained updates after the page is refreshed.
* Prevented schema changes from being lost during subsequent test execution.
* Verified the fix across Concept, Preprod, and production environments.

</details>
{% endupdate %}

{% update date="2026-10-02" %}

## Highlights

* **Reveal and update OAuth credentials on existing IFS connectors** - view OAuth Client IDs and update OAuth credentials directly on existing IFS connector variants without recreating them.

## New features

<details>

<summary><strong>Reveal and update OAuth credentials on existing IFS connectors</strong></summary>

Admins can now view OAuth Client IDs and update OAuth credentials directly on existing IFS connector variants without recreating them.

**Customer benefit:** Teams can quickly look up Client IDs for IAM troubleshooting and update rotated credentials without rewiring dependent workflows.

**What changed**

* Added a visibility toggle next to the **OAuth Client ID** field on existing connectors so users can view or copy the value.
* The **OAuth Client ID** and **OAuth Client Secret** fields are now editable on existing connectors.
* The **OAuth Client Secret** remains write-only and hidden for security.
* Verified support across the IFS connector variants listed in the implementation comments: **IFSCloud24R2**, **IFSCloud25R1**, **IFSCloud25R2**, **IFSCloud26R1**, **IFSCloud26R2**, **IFSCloud**, and **IFSAPPS10**.

<figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2F9kfUL9mvqSefELanLiqP%2Fimage-20261002-112750.png?alt=media&amp;token=c8b32352-63f4-492b-bc46-8099f3c347cb" alt=""><figcaption></figcaption></figure>

</details>
{% endupdate %}

{% update date="2026-09-25" %}

## Highlights

* Environment variables can now be managed directly in Digital Worker and Skill settings.
* Authors can use @ search to insert environment variable references more quickly and consistently.
* IFSAPPS10 connector setup is clearer with Azure Tenant ID shown only when Azure AD is selected.
* Internal role and access-management updates support governance and operational administration.

## New features

<details>

<summary><strong>Environment variable management for Digital Workers and Skills</strong></summary>

Environment variables can now be defined directly in Digital Worker and Skill settings, making it easier to manage reusable values such as base URLs and other configuration inputs.

**Customer benefit:** teams can manage environment-specific settings more safely and consistently without hardcoding values into configurations or instructions.

**What changed**

* UAT and Production workspaces maintain their own environment variable values independently.
* In UAT, users can add, edit, and delete variables.
* In Production, variable names are read-only while values remain editable.
* Environment variables are included in settings visibility and configuration flows during import and export activities.

<div><figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2FYvDIUNUplqGMupJdAYZy%2Fimage-20260904-111515.png?alt=media&amp;token=bdcfc8a7-2091-407b-9cb7-a5ec46fbc783" alt=""><figcaption></figcaption></figure> <figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2FxAWDl0Vu00vo0VLT3kRY%2Fimage-20260904-111406.png?alt=media&amp;token=386c331a-d73b-4823-8bcd-63a2000f2b62" alt=""><figcaption></figcaption></figure></div>

</details>

<details>

<summary><strong>@ attribute search in Digital Worker and Skill instructions</strong> </summary>

An `@` attribute autocomplete experience is available in the Instructions editor for Digital Workers and Skills.

**Customer benefit:** users can insert environment variable references more quickly and accurately while creating instructions.

**What changed**

* Typing `@` followed by at least three characters starts a search of configured environment variables.
* Selected values are inserted automatically in the `${env.attributeKey}` format.
* Multiple environment variable references can be inserted into the same instructions content.

<figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2FYQx0BFHx6WLnbxjxJkmF%2Fimage-20260904-112312-20260925-100414.png?alt=media&amp;token=3fbbd5e3-f34f-49b2-885d-b8171ccaada6" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>@ attribute search in intent-based output formats</strong></summary>

The same `@` attribute search capability is available in Intent-Based Output Format fields used when configuring a State.

**Customer benefit:** this helps authors create responses and field descriptions faster while keeping environment variable usage consistent.

**What changed**

* Available in both **Attribute Description** and **Submit Message** fields.
* Typing `@` followed by at least three characters searches saved environment variables.
* Selected attributes are inserted in the `${env.attributeKey}` format and can be used multiple times in the same field.

<figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2FEc3CGbYaiTQH2m98ouKi%2Fimage-20260904-112604-20260925-100504.png?alt=media&amp;token=bbd74978-7a66-4fb2-8090-e7f9cd8f37f7" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Dependent Azure Tenant ID field for IFSAPPS10 connectors</strong></summary>

The IFSAPPS10 connector configuration now supports conditional field rendering for Azure AD authentication.

**Customer benefit:** admins see the Azure Tenant ID field only when it is relevant, making connector setup clearer and reducing unnecessary configuration fields.

**What changed**

* The **Azure Tenant ID** field is shown when the selected identity provider or authentication mode is Azure AD.
* The field remains hidden for other authentication choices where an Azure Tenant ID is not required.
* This improves the IFSAPPS10 connector setup experience by aligning required fields with the selected authentication method.

</details>

## Internal Changes

The following updates are intended for internal administration, governance, and operational support. They are not customer-facing product capabilities.

### Internal FDE role in Agentic Studio <a href="#internal-fde-role-in-agentic-studio" id="internal-fde-role-in-agentic-studio"></a>

A new **FDE** role is available for internal operational users who require broader Agentic Studio access for workspace support and governance, without granting full Super Admin permissions.

**Internal purpose:** this role is intended for internal teams only and is not exposed to customers.

**What changed**

* FDE users can use Admin-level Agentic Studio capabilities needed for internal support.
* FDE users can view audit logs for Digital Workers and Skills.
* FDE users can create, edit, and delete Workspaces, and access all Workspaces by default for operational support.
* FDE users can see the `Copy UUID` option when importing Digital Worker or Skill templates.
* FDE access remains limited to Agentic Studio and does not include CX-only areas or Super Admin-only capabilities such as Entitlements.

### Role-based visibility for FDE user counts <a href="#role-based-visibility-for-fde-user-counts" id="role-based-visibility-for-fde-user-counts"></a>

A dedicated Forward Deployed Engineer user-count card is available in Access Management for internal governance and operational oversight.

**What changed**

* The FDE user-count card is visible only to users with FDE or Super Admin privileges.
* Other users do not see this administrative count.

<figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2FuJquQKD4XzpgjmKYtNDT%2Fimage-20260925-093821-20260925-100534.png?alt=media&amp;token=8e135737-a469-40c1-99e6-be9da691f514" alt=""><figcaption></figcaption></figure>
{% endupdate %}

{% update date="2026-09-22" %}

## Highlights

* [<mark style="color:violet;">**MetaPrompter enhancements:**</mark>](/agentstudio/resource-library/explainers/the-metaprompter-customizing-with-plain-language.md) expanded natural-language capabilities for building and extending agents, including code generation, in-chat creation of tools and skills, richer structured outputs, and marketplace-ready reuse.&#x20;
* **Application Builder&#x20;*****(new)*****:** generate a complete application, not just a single agent, from a natural-language description.&#x20;
* [<mark style="color:violet;">**Digital Crew**</mark><mark style="color:violet;">**&#x20;**</mark>*<mark style="color:violet;">**(new)**</mark>*](/agentstudio/resource-library/explainers/digital-crew-coordinated-digital-workers-for-end-to-end-processes.md)**:** coordinated teams of Digital Workers that own an entire business process end-to-end, rather than a single micro-process.&#x20;
* **Ontology&#x20;*****(new):*** a shared knowledge model that gives every agent and application on the platform a consistent understanding of business entities and relationships.&#x20;

This release extends the IFS Loops platform's agentic foundation — the capabilities that let every Digital Worker, application and automation on the platform be built, connected and governed consistently. It brings meaningful enhancements to Metaprompter, introduces Application Builder as a new way to generate complete applications from natural language, previews Digital Crew as the platform's next step beyond single-purpose Digital Workers, and strengthens the shared Ontology that underpins how agents and applications understand the business.&#x20;

Together, these capabilities make it faster to go from a business idea to a working agent, application, or coordinated team of agents — with less manual configuration and greater consistency across what gets built.&#x20;

### Core Platform Capabilities

<details>

<summary><a href="/agentstudio/resource-library/explainers/the-metaprompter-customizing-with-plain-language.md"><mark style="color:violet;"><strong>MetaPrompter Enhancements</strong></mark></a></summary>

MetaPrompter is the natural-language interface within Agentic Studio for building and editing agents. Instead of working through configuration screens, users describe what they want an agent to do — for example, “Create an agent that monitors support tickets, classifies urgent ones, and sends a Slack notification to the escalation channel” — and MetaPrompter generates the instructions, tools, connectors and triggers needed, updating a visual graph of the agent as it goes. Changes are always made in a safe UAT environment first and promoted to production through a controlled step.

**Key Capabilities**

* Coding-agent mode, so MetaPrompter can generate and edit code-level logic in addition to configuration.&#x20;
* Create a new IFS tool directly from a MetaPrompter conversation, powered by the IFS Intelligence MCP.&#x20;
* State-based outputs and output attributes, for richer, structured agent responses.&#x20;
* Create a new Skill directly from chat, using the same natural-language flow used for tools.&#x20;
* Add system tools to an agent directly from the MetaPrompter conversation.&#x20;
* Marketplace visibility for tools, skills and components created through MetaPrompter, so they can be reused across workspaces.

</details>

<details>

<summary><strong>Application Builder</strong></summary>

Application Builder is a new Agentic Studio capability that extends natural-language creation from a single agent to a complete application. Users describe the application they need, and a meta-agent generates the working application — its logic, its user interface, and its integrations — ready to be hosted on IFS.

**Key Capabilities**

* Natural-language application generation, powered by a dedicated meta-agent.
* Direct connection to MetaPrompter, so the same conversational experience used to build agents extends to building applications.&#x20;
* Support for MCP-based integrations within generated applications.&#x20;
* Hosting of generated applications directly on IFS.&#x20;

{% hint style="info" icon="lightbulb-exclamation-on" %}
*Availability: Early Access. Application Builder is being introduced as a preview capability, with broader availability planned in an upcoming release*
{% endhint %}

</details>

<details>

<summary><a href="/agentstudio/resource-library/explainers/digital-crew-coordinated-digital-workers-for-end-to-end-processes.md"><mark style="color:violet;"><strong>Digital Crew</strong></mark></a></summary>

Digital Crew is the platform's next step beyond single-purpose Digital Workers: a coordinated team of Digital Workers that owns an entire process — from first touch to final step — so nothing falls through the cracks between individually automated tasks.

**Sample crew workflows are being defined across four domains:**

1. **Field Service Management:** First Time Fix, Proactive Maintenance, SLA Priority, Repeat Visit Prevention, Revenue Recovery
2. **Procurement**
3. **Enterprise Asset Management**
4. **Finance:** Faster Close, Cash Visibility, Touchless Transactions

</details>

<details>

<summary><strong>Ontology</strong></summary>

Ontology is the platform's shared knowledge model — a structured map of business entities, attributes and relationships that MetaPrompter and Application Builder both draw on when creating new agents, tools and applications. Rather than each agent or application defining the business on its own terms, they share a common, evolving understanding of it. This reduces rework, improves consistency across what gets built on the platform, and makes new agents and applications faster to generate accurately.

</details>

### New Features

<details>

<summary><strong>Usage Tracking</strong></summary>

**What is Usage Tracking?**

Usage Tracking gives visibility into how Digital Workers are actually being used — every invocation, the outcome it produced, and the underlying model activity behind it — captured consistently across the platform rather than left to each Digital Worker to report on its own.&#x20;

Rather than building a separate, platform-specific analytics layer, IFS Loops connects this telemetry to Paid.ai, a business engine purpose-built to turn agent activity into usage and billing records. IFS Loops focuses on capturing accurate, complete telemetry from every Digital Worker; Paid.ai turns that telemetry into the usage insight, invoicing and revenue reporting that follow from it.&#x20;

**Summary of Benefits**

* Every Digital Worker's usage is captured the same way, at the source, with complete traceability back to the interaction that produced it.&#x20;
* Usage and billing analytics are handled by Paid.ai, a platform purpose-built for that job, instead of a bespoke build IFS Loops would otherwise have to maintain.&#x20;
* Activity can be understood in the commercial terms that fit the process — per agent, per action, per workflow, or per outcome.&#x20;
* Consistent usage data becomes a foundation for governance, audit and commercial reporting alike, not a one-off report.&#x20;
* Usage and cost are visible directly in IFS Loops Studio, scoped per tenant and per workspace, without needing a separate reporting tool.&#x20;

</details>

<details>

<summary><strong>LLM Guardrails: Prompt Injection &#x26; Jailbreak Protection</strong> </summary>

**Highlights**

**What shipped:** &#x20;

* Input-screening guardrails for Digital Workers built on NVIDIA NeMo Guardrails, protecting against prompt injection and jailbreak attempts.&#x20;
* Multi-layer detection: fast regex pattern checks, followed by an LLM-based safety judge (currently evaluating Qwen3Guard-4B).&#x20;
* Coverage for both direct input (user-typed prompts) and indirect input (documents/invoices the Digital Worker fetches, including OCR'd scanned content).&#x20;

**Why it matters:** &#x20;

* Prevents attempts to override Digital Worker instructions, exfiltrate data, or bypass approval steps (e.g., approving a payment without the required approval workflow).&#x20;
* Reduces risk from both directly typed attacks and indirect attacks hidden inside supplier/invoice documents — a scenario not well covered by generic industry benchmarks.&#x20;

**Who benefits:** &#x20;

* Builders and operators of IFS Loops Digital Workers who need assurance that ERP-facing agents (invoices, POs, supplier data) are protected from malicious or manipulated input.&#x20;

**New Capabilities**

* **Guardrail Orchestration:** &#x20;
  * Central decision point that routes all untrusted text (typed or fetched) through the same screening pipeline before it reaches the main LLM.&#x20;
* **Layered Screening Engine:** &#x20;
  * Layer 1 – instant regex rules for obvious attack patterns (e.g., “ignore instructions”).&#x20;
  * Layer 2/3 – model-based classification for semantic and novel attack detection, now standardized on Qwen3Guard-4B.&#x20;
* **Indirect-Injection Coverage:** &#x20;
  * OCR pipeline added so text hidden inside scanned invoices/images is screened the same as typed text.&#x20;
* **IFS-Tuned Evaluation:** &#x20;
  * Testing extended beyond generic public benchmarks to an IFS procurement/ERP-specific dataset to better reflect real Digital Worker risk (e.g., PO/invoice vocabulary, tool-call abuse).&#x20;

**Known Limitations / In Progress**&#x20;

* **Jailbreak-detection accuracy** is currently below target on IFS-tuned test cases and is being iterated on; prompt-injection detection is already performing well.&#x20;
* **End-to-end latency** of the multi-layer check is being measured and optimized; current runs show multi-second average latency per request.&#x20;
* **Final approach/model selection** will be confirmed once IFS-tuned dataset testing concludes.&#x20;

</details>
{% endupdate %}

{% update date="2026-09-18" %}

## Highlights

* **Adoption metrics and community ratings** on the Global Marketplace, giving teams clear visibility into template popularity and effectiveness.
* **Private 1:1 messaging in Microsoft Teams** for AI Agents and Human-in-the-Loop workflows.
* **Native IFS Model Context Protocol (MCP) Server** connector integration for rapid tool discovery and schema import.
* **Stronger runtime protection** preventing accidental deactivation of Digital Workers deployed in active widgets or Autopilot.
* **Enhanced canvas and navigation reliability**, including Fit View graph controls, streamlined version selection, and seamless Teams personal app navigation.

This release focuses on improving template discovery and adoption tracking in the Global Marketplace, expanding Microsoft Teams collaboration with direct 1:1 user messaging, introducing native MCP connector support, and reinforcing operational safeguards for active digital workers, alongside usability and navigation fixes across the canvas and integration workflows.

## New features

<details>

<summary><strong>Marketplace and digital worker lifecycle</strong></summary>

**Better visibility into marketplace adoption and template origins**

* Global Marketplace entries now provide clearer signals to help teams decide which templates to use.&#x20;
* Digital Workers and Skills display total download counts and average user ratings directly on cards and detail views, making it easier to identify popular and well-received templates.&#x20;
* Imported templates also now show where they came from, such as the Global Marketplace, Local Marketplace, or a ZIP package, and ZIP-based imports start with a clear initial version.

**Safer digital worker lifecycle management and improved dashboard collaboration**

* Digital worker administration is now more resilient and collaborative.&#x20;
* The platform prevents deactivation when a digital worker is still actively used in Autopilot, Application Widgets, or Collaboration Widgets, reducing the risk of accidental disruption.&#x20;
* Dashboard updates can also now be published more deliberately, helping teams share finalized analytics and workspace views with the right users.

</details>

<details>

<summary><strong>Integrations and conversational extensions</strong></summary>

**Private direct messaging for AI Agents in Microsoft Teams**

* Microsoft Teams integration now supports direct 1:1 conversations between users and AI Agents in addition to group channels.&#x20;
* This enables more targeted Human-in-the-Loop interactions and private follow-ups, while preserving conversation continuity when a user replies back in the bot chat.

**Expanded connector support and more flexible channel associations**

* Agentic Studio now includes native support for the IFS Model Context Protocol Server, allowing teams to discover and import MCP tools directly from the integrations catalogue with ready-to-use schemas.&#x20;
* Homepage channel configuration has also been expanded so a single channel can be associated with multiple digital workers, making deployment patterns more flexible.

</details>

<details>

<summary><strong>Operational access</strong></summary>

**New Ops role for operational users**

* A new Ops role has been introduced to give operational users the right level of access across Agentic Studio without requiring elevated Admin permissions.
* This helps teams separate day-to-day operational responsibilities from full administrative access while keeping cross-environment workflows available to the right users.

</details>

## Bug fixes

<details>

<summary><strong>Studio canvas and navigation</strong></summary>

**Improved canvas viewing and version navigation**

* The authoring experience is now smoother when working with complex digital worker workflows and multiple saved versions.&#x20;
* The Fit View control on the canvas now correctly centers and scales the graph, while the version selector has been refined to make working drafts easier to find and switch to.

</details>

<details>

<summary><strong>Authentication and integrations reliability</strong></summary>

**More reliable Teams navigation and tool authentication**

* Several fixes improve reliability across Teams-based workflows and connected tools.&#x20;
* The Teams Personal App now handles unavailable default integrations more gracefully, Human-in-the-Loop notification links route more consistently, and invoice generation flows no longer fail because of incorrect authentication handling in valid sessions.

</details>

<details>

<summary><strong>Authentication and integrations reliability</strong></summary>

**More reliable Teams navigation and tool authentication**

* Several fixes improve reliability across Teams-based workflows and connected tools.&#x20;
* The Teams Personal App now handles unavailable default integrations more gracefully, Human-in-the-Loop notification links route more consistently, and invoice generation flows no longer fail because of incorrect authentication handling in valid sessions.

</details>

## Internal administrative updates <a href="#internal-administrative-updates" id="internal-administrative-updates"></a>

<details>

<summary><strong>Visibility</strong></summary>

**Super Admin audit visibility for marketplace and import activity**

* Additional audit visibility has been introduced for internal governance purposes.&#x20;
* Super Admin users can now review marketplace interaction history and template movement more effectively, including activity related to downloads, ratings, local marketplace usage, and import source tracking.

</details>

{% endupdate %}

{% update date="2026-09-04" %}

## Highlights <a href="#highlights" id="highlights"></a>

* **Better Copilot usability:** the Ask experience is now easier to discover and use directly within the widget.
* **More reliable template handling:** Digital Worker and Skill JSON is automatically validated and normalized during download and upload flows.
* **Broader content-management coverage:** publicly accessible Fluid Topics content, SkillJar content, and IFS Cloud KB article attachments are now better supported.
* **Improved Teams collaboration:** HITL messages in Microsoft Teams can support tagging users.
* **Improved alert clarity:** sentiment notifications now provide more actionable context behind score changes.
* **Higher platform stability:** fixes address output rendering, Production Digital Worker responsiveness, Skill tool loading, and Microsoft Teams tab setup.

This production release focuses on improving usability, strengthening template reliability, and resolving issues that affect everyday customer workflows across Copilot, Digital Workers, Skills, and Microsoft Teams integration.

**What’s included:**&#x20;

* Better visibility for the Ask experience in the Copilot widget
* Automatic validation and normalization of Digital Worker and Skill templates during download and import
* Richer sentiment-alert drilldown context
* Added content-management connectors for publicly accessible Fluid Topics content, SkillJar, and IFS Cloud KB article attachments
* HITL Microsoft Teams user tagging
* Fixes for state-based output rendering, Production Digital Worker responsiveness, Skills tool loading, and Microsoft Teams tab setup.

## New features

### Usability

<details>

<summary><strong>Sentiment alerts now include deeper drilldown context</strong></summary>

Sentiment notifications have been enhanced to provide clearer context about why a score has decreased, including the underlying drivers that contributed to the change.

**Customer benefit:** teams can understand negative sentiment shifts faster and take action sooner without needing to manually investigate each case in detail.

**What changed**

* Alerts can now surface more detailed reasons behind a score drop.
* This may include contributing sentiment tags, phrases, or tone indicators that explain the decline.
* Users get more immediate context directly from the notification experience.

</details>

<details>

<summary><strong>Ask is now more prominent in the Copilot widget</strong></summary>

The Ask experience has been moved to a more visible position within the Copilot widget so users can enter questions more naturally while staying in context.

**Customer benefit:** this improves discoverability and encourages faster adoption by making it easier for agents to ask questions without leaving their current workflow.

**What changed**

* The Ask input is displayed directly below the widget section for easier access.
* The text box remains visible while users browse widget content such as intents, resolutions, insights, and comments.
* Selecting the Ask button places focus into the input so users can begin typing immediately.

<figure><img src="https://1875689104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzpOPAqpE6CRlx7tqonUl%2Fuploads%2FIrxYtro1K2NzOxXy1Z63%2Fimage-20260904-120130%20(1).png?alt=media&amp;token=e5dcf0d0-3acb-4235-b12e-0ffecfed4bd9" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Content-management integrations expanded for Fluid Topics, SkillJar, and KB attachments</strong></summary>

Release 0.8 includes additional content-management capabilities across integrations and core services, covering publicly accessible Fluid Topics content, SkillJar connector support, and attachment retrieval for IFS Cloud KB articles.

**Customer benefit:** teams can bring more external and knowledge-base content into Loops workflows with less manual handling and better connector coverage.

**What changed**

* Added support for fetching publicly accessible Fluid Topics content that does not require users to sign in or provide additional authorization.
* Implemented SkillJar as a ContentManagement integration, including API configuration, authentication, content fetching, mapping, error handling, and test connection support.
* Added support for pulling Knowledge attachments for IFS Cloud KB articles.

</details>

<details>

<summary><strong>HITL messages in Microsoft Teams now support tagging users</strong></summary>

Human-in-the-loop Microsoft Teams messages have been enhanced to support tagging or mentioning users directly in Teams messages.

**Customer benefit:** teams can draw the right person’s attention to HITL requests faster, improving collaboration and response times in Teams-based workflows.

**What changed**

* Added support for tagging users in HITL Teams messages.
* Aligns Teams HITL behaviour with the expected Microsoft Teams mention experience.

</details>

### Improvement

<details>

<summary><strong>Digital Worker and Skill templates are now validated automatically during download and import</strong></summary>

Template handling has been improved by validating and normalizing Digital Worker and Skill JSON in both export and import flows.

**Customer benefit:** this reduces template compatibility issues, lowers the chance of import failures, and helps ensure downloaded templates stay aligned with the latest expected schema.

**What changed**

* Before download, JSON is validated against the latest schema and missing required keys or objects are added automatically where needed.
* Before upload or import, templates are validated again and normalized when possible.
* Existing valid data is preserved while missing defaults are added safely.
* If a template cannot be normalized, users receive a clearer validation error instead of a later-stage import failure.

</details>

### Bug Fixes

<details>

<summary><strong>Rendering issue resolved for state-based outputs when Retrieval is the last tool</strong></summary>

A fix has been delivered for an issue affecting state-based output rendering when Retrieval was configured as the final tool in the flow.

**Customer benefit:** output experiences are now more consistent and reliable in retrieval-based scenarios, reducing confusion and unexpected response behavior.

**What changed**

* Resolved a rendering issue that impacted state-based outputs in workflows ending with Retrieval.
* Improves consistency between configured tool behavior and the final presented output.

</details>

<details>

<summary><strong>Production Digital Workers now respond more reliably</strong></summary>

An issue affecting responsiveness for the Supplier Order Manager and Supplier Invoicing Manager Digital Workers in Production has been resolved.

**Customer benefit:** users can once again rely on these Digital Workers to process and respond to queries in live Production use cases.

**What changed**

* Fixed the issue preventing the affected Digital Workers from responding to user queries in Production.
* Restores expected conversation behavior for these live customer-facing assistants.

</details>

<details>

<summary><strong>Skills-associated tools now load correctly on Concept environments</strong></summary>

Resolved an issue where the Meta API failed when users navigated to tools associated with a Skill on Concept environments.

**Customer benefit:** users can move through the Skills experience more smoothly without interruptions when reviewing associated tools.

**What changed**

* Corrected the failure impacting tool loading inside the Skills module.
* Improves reliability when opening Skills that include associated tools.

</details>

<details>

<summary><strong>Microsoft Teams tab setup no longer shows a misleading error</strong></summary>

Fixed an issue where adding the IFS Bot to a Microsoft Teams channel briefly displayed an error message even though the tab was added successfully.

**Customer benefit:** users now get a cleaner, more trustworthy setup experience when adding the bot in Teams.

**What changed**

* Removed the transient error message shown during IFS Bot tab creation.
* Tab setup now completes without displaying a false failure message.

</details>

{% endupdate %}

{% update date="2026-04-30" %}

## Highlights

* **What shipped:** MetaPrompter, ADLC enhancements (build flow + template import/export), marketplace/templates, and evaluation + regression testing
* **Why it matters:** Improves predictability and testability of Digital Workers, accelerates iteration on instructions and configurations, and strengthens confidence for production rollouts
* **Who benefits:** Builders and operators of Digital Workers who need consistent outputs, faster iteration, and higher-confidence releases

## New features

### Usability

<details>

<summary><a href="/agentstudio/resource-library/explainers/understanding-the-agent-development-life-cycle-adlc.md"><strong>Agent Development Lifecycle (ADLC)</strong></a></summary>

*This release delivers new and enhanced capabilities for building and managing Digital Worker (DW) templates, deployment, testing, and versioning. The Agent Studio now provides:*

* Enhanced Digital Worker build flow
  * Guided build flow for Digital Workers: Create → Instructions → Tools → Skills → Triggers → Settings
  * Instructions as the core control plane: define persona/role, context, guardrails, tool usage, response structure, and multi-step reasoning
  * Tool management is simplified, with connector-based standard tools and custom tool creation as needed
  * Skills as reusable reasoning patterns (prompt, reasoning, and domain skills) to standardize high-quality outputs
* Import/Export of Digital Workers
  * Export as Template workflow with guided checklist (e.g., overview → integrations → branding & metadata → review & export) to make installations predictable and secure
  * Export summary provides an at-a-glance inventory of what’s included (e.g., number of skills, tools, and triggers) and allows editing the system description shown to installers
  * Clear scoping during export: exporting affects the template package only (does not modify the live system)
  * Marketplace import includes an install readiness checklist and surfaces required integrations/connectors that must be configured before the agent can be installed

</details>

<details>

<summary><a href="/agentstudio/resource-library/how-to-guides.md#how-to-find-and-use-the-marketplace"><strong>Marketplace &#x26; Templates</strong></a></summary>

* New marketplace experience to discover industrial AI agents and deploy enterprise-grade solutions
* Browse and filter by categories (e.g., Quality Control, Predictive Maintenance, Automation, Supply Chain, Safety & Compliance, Process Optimization, Operations, Logistics)
* Search across agents, categories, and features; preview and view agent details before deployment
* Agent cards highlight key signals such as ratings, last-updated date, usage/downloads, and badges (e.g., Trending, Popular, New, Stable)

</details>

<details>

<summary><a href="/agentstudio/resource-library/explainers/the-metaprompter-customizing-with-plain-language.md"><strong>MetaPrompter</strong></a></summary>

* Scope (Q1 2026): available for **editing existing Agents** only
* Interactive prompt designer that generates structured instructions
* Enforces state-based output formats for consistent, predictable behavior
* Supports iterative instruction updates to accommodate customer-specific rule changes without code

</details>

### Memory Management

<details>

<summary><strong>Long-term memory per entity (Memory maps)</strong></summary>

* Dual-path memory initialization: combine continuous entity-specific learning with optional user-defined Rule Books for bootstrapping
* Captures learnings from HITL feedback to evolve instructions and long-term memory over time
* Designed to improve resilience to variable inputs (e.g., changing document formats and incomplete data)

</details>

### Monitoring

<details>

<summary><strong>Dashboards</strong></summary>

* Digital Worker Activity overview with trend charts and KPI tiles (e.g., total events, HITL conversations, total tests)
* Current Activity snapshot (active Digital Workers, active conversations)
* Flow monitoring with completion visibility (Digital Worker flows and close rate)
* Leaderboards for operational triage (Top Digital Workers; HITL conversations by agent)
* Governance/quality surfaces (Eval failures) and cost visibility (token usage by agent)

</details>

<details>

<summary><strong>Evals</strong></summary>

* Dataset-based eval runs with scorecards across key dimensions (Accuracy, Relevance, Helpfulness), plus operational metrics (tests run, success rate, failures, average latency)
* Per-test-case drill-down: view the agent plan, conversation transcript, and detailed rubric scoring with reasoning to support faster debugging and iteration
* Run history tracking to compare results over time and spot regressions

</details>

<details>

<summary><strong>Regression testing</strong></summary>

* Organize tests into datasets with individual test cases and pass/fail status tracking
* Run history captures when an eval was executed and by whom, making it easier to compare runs and detect regressions
* Performance signals included alongside quality (e.g., per-test latency and average runtime) to catch speed/timeout failures early

</details>

### Additional notes

<details>

<summary><strong>Improvements</strong></summary>

* Deterministic intent based agent output
* Predictable responses for machine interaction (schema/state-based output normalization)
* MS Teams Adaptive cards support

</details>

<details>

<summary><strong>Security &#x26; compliance</strong></summary>

* None

</details>
{% endupdate %}
{% endupdates %}