Skip to main content

Release 0.5.13 — Service Accounts, RAG File Uploads, and Slack Identity Routing

Released: 2026-06-15 Chart: oci://ghcr.io/cnoe-io/charts/ai-platform-engineering:0.5.13 Previous release: 0.5.12

Highlights

0.5.13 ships Service Accounts — team-owned bot identities you can use to run agents and tools on behalf of your team without tying execution to a personal account. RAG now accepts local file uploads directly in the admin UI. Slack gains identity-aware routing so messages can be sent as a specific user or service account.

What's New

Service Accounts

  • Team-owned bot identities — teams can now create service accounts: non-personal identities that belong to the team, can be granted tool access, and run agents as a known, auditable principal rather than an individual user's account
  • Credential passthrough — service accounts can carry their own credentials into tool calls, so integrations like GitHub or Jira authenticate with the service account's token rather than the invoking user's

Knowledge Base (RAG)

  • Local file upload ingestion — you can now drag and drop files directly in the admin Knowledge Base panel to add them to the RAG index, without needing an external ingestor pipeline

Slack

  • Run As identity — Slack channels can be configured to send messages as a specific user or service account, giving teams a consistent identity for bot-driven conversations and clear audit trails
  • Unlinked-user fallback — Slack messages from users who haven't linked their account now fall back gracefully instead of failing silently

MCP Tools

  • Jira: assign issue — a new "Assign Issue" action is available in the Jira MCP tool, using the correct Jira API endpoint so assignments succeed on all Jira project types

Setup

  • Production-ready setup scriptsetup-caipe.sh now handles domain/TLS configuration, Keycloak setup, and dynamic agent registration end-to-end, making it usable for production deployments rather than just local testing

Bug Fixes

  • Webex routing — stale Webex agent route mappings are now replaced correctly when configuration changes, preventing messages from being routed to the wrong agent
  • AgentGateway config — the config bridge now fetches its target list from the platform API rather than reading the database directly, closing a gap where stale config could cause routing failures

Breaking Changes

No breaking changes. Drop-in upgrade from 0.5.12.

Upgrade

helm upgrade ai-platform-engineering \
oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
--version 0.5.13 \
-f your-values.yaml

No Helm values changes between 0.5.12 and 0.5.13. No data migrations required.