🚀 arnold™ 1.2.0
- NA Release Date: 2026-09-28
- EU Release Date: 2026-10-01
arnold™ 1.2.0 improves group-based access controls, Cloud UI app management, custom tool configuration, and audit tracking. It also provides better visibility into which MCP clients are using the newer MCP version.
👥 Stronger Group-Based Access Controls
What it is
Group management now provides more precise access controls for connections and MCP requests. Connection visibility is filtered according to user role, group ownership, and client access. MCP requests are checked against tenant and client group membership when group management is enabled.
Why it matters
- Helps ensure users see only the connections available to them
- Enforces group membership checks for MCP access
- Gives administrators and regular users access appropriate to their roles
☁️ Cloud UI App Import & Export
What it is
Cloud UI app configurations can be imported and exported, with validation and audit tracking for import operations.
Why it matters
- Makes it easier to reuse and transfer app configurations
- Helps catch issues during configuration import
- Improves traceability of configuration changes
🧰 More Reliable Custom Tool Configuration
What it is
Custom tool templates are checked for syntax issues before they are saved. Configuration references in templates and scripts now report errors when values are missing or unassigned.
Why it matters
- Helps identify template problems before a tool is used
- Makes missing configuration easier to diagnose
- Reduces unexpected behavior caused by incomplete settings
🔎 Improved Audit Tracking
What it is
Audit tracking has been expanded for language model and feature changes, with improvements to change details and user identification.
Why it matters
- Provides clearer records of important configuration changes
- Makes it easier to understand who made a change and what was affected
- Supports troubleshooting and operational oversight
🐞 Bug Fixes & Stability
What it is
This release fixes an issue that could create duplicate tenants when concurrent consent callbacks were processed. It also improves configuration handling and audit-log behavior, as well as better analytics for tracking client MCP versions.
Why it matters
- Prevents duplicate tenant records caused by concurrent requests
- Keeps audit information within the correct tenant context
- Makes configuration errors clearer and easier to resolve