For the complete documentation index, see llms.txt. This page is also available as Markdown.
June 24
Agents
OAuth 2.0 support for MCP Server Trigger
You can now enable OAuth 2.0 authorization directly on the MCP Server Trigger, 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.
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.
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.
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.
