CAIPE 1.2.0 brings a unified chat history, message editing with conversation rewind, and a context-remaining indicator to web chat, plus native rich-text support for Jira. It also widens team-based management permissions and fixes a batch of authorization audit gaps that were undercounting or hiding real activity.
CAIPE 1.1.1 corrects the Helm security defaults that stopped Milvus and Keycloak initialization jobs from starting after the 1.1.0 upgrade. It also makes large service-account datasource grants easier to manage.
CAIPE 1.1 adds scheduled and webhook-triggered agent runs, Projects and hosted agentic applications, clearer RAG permissions, and opt-in DocumentDB support. It also moves the platform to Python 3.14 and Node.js 24, improves streaming and audit behavior, and hardens the Helm chart's workload defaults.
Fresh setup-caipe.sh installations enable the scheduler and autonomous-agent services
by default. Operators can opt out when those capabilities are not needed.
CAIPE 1.0 brings the platform's main user experiences together around one application shell. A customizable home page, global navigation, command palette, platform-health notifications, searchable pickers, and consistent breadcrumbs make the UI easier to navigate and operate.
This release also completes the move to the CAIPE package and image namespace, expands Webex administration and self-service identity linking, and adds more governed RAG workflows for file data sources. The legacy agent-builder and legacy authorization paths are retired; dynamic agents and the centralized authorization service are the supported runtime paths.
A new UI. Navigation and settings were unified into a single application shell: one settings center instead of scattered per-area config, a coherent workspace nav, and consistent breadcrumbs, deep links, and pickers throughout. Most screens you touch daily have moved or been rebuilt.
Knowledge base access control. RAG knowledge bases are now fully governed. Ingestion sources are managed from the UI instead of YAML, gated by their own RBAC relations, and authorization is enforced at query time on the live agent tool path, so a search only ever sees datasources the caller can read.
Underneath both: the legacy supervisor and standalone A2A agents are gone, and the Centralized Authorization Service is now the single decision point for every resource.