OPAQUE 2.6.1¶
February 10, 2026
This update introduces runtime context mapping for the MCP API Tool, making it easier to build adaptive, secure agentic workflows that respond to who’s running them.
New features and enhancements¶
- Runtime context mapping in the MCP API Tool: You can now map runtime values (like user roles or IDs) to API parameters using a new context mapping dialog. The UI allows you to select target parameters from the OpenAPI spec via drop-down menus, making it easy to personalize workflow behavior based on who’s running it—without changing the workflow itself.
- Expanded trace visibility in the UI: The workflow trace view now shows live status, run duration, and active nodes during execution. You can view trace details for each node, including elapsed time, tool traces, and status. For agent nodes, connected tools now appear in a new box below the node and are clearly labeled with their icons. The trace dialog also includes a complete input/output record and full trace JSON for deeper inspection. For details see Using test mode
- Workflow input context propagation: You can now define input values that are passed to tools dynamically through the mapped fields during workflow execution. This makes workflows more flexible and reduces the need for hardcoded configuration.
Fixed issues¶
- Workflows chaining a RAG agent to the OPAQUE Redact Service no longer fail due to mismatched input field names. This resolves a compatibility issue that previously caused RAG output to break when passed to the Redact service.
- Attested workflow counts in the Trust tab now display accurately when multiple workspaces share the same name.
Known issues¶
| Issue | Suggested workaround |
|---|---|
| Attestation report header may cause errors under high load. Enabling the header can trigger a race condition when multiple concurrent requests (≥3) attempt to generate reports, leading to failures. | Enable the header only once per workflow session, not per request. A server-side fix is under consideration. |
| Session may hang after returning to the app: If you close the app and return after ~10 minutes, the app may get stuck loading. | Refresh your browser window. |
| Guardrails are not supported when using GPT-5 (a model limitation). | Use GPT-4 as the engine when guardrails are required. |
| Guardrails are not supported when using Anthropic. | None. |
| Workflows may time out when running with high temperature settings. | Lower the temperature value, or increase the timeout setting in the SDK. |
| The Context input port on the OpenAI agent is not currently functional. | None. This will be fixed in a future release. |