> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/release-notes/june-2026/june-24.md).
# June 24
## :sparkles: **Agents**
### **OAuth 2.0 support for MCP Server Trigger**
You can now enable OAuth 2.0 authorization directly on the [MCP Server Trigger](/documentation/connectors-and-triggers/triggers/web-protocols/mcp-server.md), allowing external agents to securely access resources on behalf of a user.
Users authenticate with your OAuth provider and explicitly grant permission to the agent, eliminating the need for custom authorization logic outside the platform while improving security and compliance. Compatible with OpenAI Agent Builder, Claude Desktop, and Cursor.
Learn [how to configure OAuth 2.0 on the MCP Server Trigger](/documentation/connectors-and-triggers/triggers/web-protocols/mcp-server/how-to-configure-oauth-2.0-on-the-mcp-server-trigger.md).
## :rocket: **Platform Improvements**
### **Execution source identification in Monitor**
The **Source** field in the Monitor Executions page now distinguishes between internal test runs and external trigger calls.
When a pipeline is executed from inside the Digibee platform, the field displays **"test"**; when triggered externally after deployment, it displays the **trigger name**. This makes it easier to identify the origin of each execution at a glance.
See the [Executions documentation](/documentation/developer-guide/development-cycle/dashboards/completed-executions.md) for more information.
### **API Trigger opens on the Endpoints tab when editing**
When editing a pipeline created with the API Trigger, the configuration now opens directly on the **Endpoints** tab to facilitate endpoint configuration. When creating a new pipeline with the API Trigger, the configuration continues to open on the **General** tab.
Learn [how to create an API pipeline](/documentation/developer-guide/development-cycle/build-overview/api/how-to-create-an-api-pipeline.md).
## :bugs: **Bug Fixes**
* **Agent Component – Regex guardrails:** Fixed an issue that prevented users from editing existing Regex guardrail rules. Guardrails can now be modified without deleting and recreating them.
* **Version Diff Viewer:** Fixed a bug where pipelines built with the MCP Server Trigger displayed only the Tool Router step in the version comparison tree. All steps are now visible when comparing versions.
* **License consumption – Consumption-Based Model:** Fixed an issue where some labels on the Consumption-Based Model page displayed **GB/s** instead of **GB-s**. All labels now display the correct unit consistently.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digibee.com/documentation/release-notes/june-2026/june-24.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.