Skip to content
KindoKindo Docs

Self-Managed 2026.09 Release Notes

Kindo 2026.09 for self-managed installs. Latest version: 2026.09.14.

2026.09.0

These notes cover everything that changed since 2026.07.

What’s new

Agents and chat

  • Skills (opt-in: SKILLS): users upload, version and share their own skill packages, attach them to agents, and run them as agent steps or chat turns.
  • OpenShell sandboxes: OpenShell is now the default sandbox for agent code execution on new installs. It runs Skills scripts and persistent workspaces.
  • Platform tools: agents can now work with Kindo itself as a first-class tool set: list agents and view their configuration, look up conversations and agent runs, and start other agents.
  • Structured conversation metadata (opt-in: CONVERSATION_METADATA): capture defined fields from conversations against a schema.
  • Persistent sandbox workspaces (now generally available; on by default for new installs): agents with a persistent workspace turned on keep each user’s working files between runs.
  • Agent runs are more durable: long runs survive worker restarts, and child agents pass their results and errors back to the parent agent.
  • Each agent can have its own default set of integrations.

Models

  • Models with multiple providers: attach several provider endpoints to one model, and Kindo fails over between them automatically. Organization admins can do this for their own models, and superadmins for global models.

Integrations

  • Government cloud integrations (early access): Microsoft GCC High and Azure Government versions of the Microsoft integrations, including Entra ID, Defender, Intune, Purview, Teams, Outlook, OneDrive, SharePoint and Sentinel.
  • Multiple connections per integration: select several connections for the same integration, and the agent picks the right account for each call.
  • Agents and users now see an integration’s own reason when it refuses a request.
  • Organization and user-group tool permissions apply everywhere agents use tools, including the /v1/mcp gateway.
  • New capabilities in GitHub, Microsoft Entra ID, SharePoint Online, ServiceNow, Splunk, Qualys, Linear and Swimlane.

Administration

  • Superadmin dashboard: administer organizations, users, models and superadmin accounts from one place, without touching the cluster.
  • Built-in single sign-on: SAML SSO now runs inside Kindo, with no separate SSO service to operate.
  • Email code and Google sign-in: besides SAML SSO, users can sign in with a one-time code sent by email. Google sign-in is also available and is off by default.
  • Managed secrets: application secrets are managed through the External Secrets Operator, which can read from your own secrets store.
  • In-cluster observability: traces, metrics and logs are collected in the cluster, with agent monitoring dashboards included.
  • Organization settings are reorganized: the Security tab is now split into Audit Log, Model Access & DLP, Integration & Tool Access, Sharing Permissions and SSO.

Security and reliability

  • Security hardening across the platform, including signed service-to-service requests, security response headers, and updated dependencies.
  • Reliability and performance improvements across ClickHouse, background workers, sandboxes, document ingestion and speech-to-text.

Upgrading from 2026.07

Follow the 2026.07 to 2026.09 upgrade guide for the detailed procedure. The items below summarize what you need to know and do.

Before you upgrade

  • Back up: take a configuration backup with the 2026.07 CLI, and snapshot your PostgreSQL databases immediately before upgrading.
  • Check prerequisites: the installer needs Helm 4.0, Helmfile 1.2, kubectl 1.32 and yq 4.0 or later, and the install contract needs an SMTP block.
  • Run kindo config migrate: it sets the new operatorEmail field from your admin email. The upgrade makes that person the first superadmin and prints their superadmin key once, so store it right away.
  • Add the superadmin hostname: add DNS and a certificate for superadmin.<your base domain>.
  • Check cluster policies: an External Secrets Operator already in your cluster must serve external-secrets.io/v1. If you enforce the baseline or restricted Pod Security level, allow the new log collector in kindo-monitoring and the sandbox pods in sandbox.
  • Carry forward Helm values: the upgrade no longer copies your previous Helm values. Run kindo upgrade --plan and save any you set on purpose with kindo config helm-override set.
  • Move model proxy clients: point anything that calls litellm.<your base domain> at the API host with a Kindo API key. That hostname stops working at upgrade.
  • Plan for SSO: SSO set up in 2026.07 stops working at upgrade, and members and admins of organizations that enforce SSO can’t sign in until they have a new SAML connection. Book each identity provider administrator into the maintenance window. If one isn’t available, turn off Require SSO for that organization in the superadmin dashboard after upgrading so its members can sign in with an emailed code, and turn it back on once its connection works.

After you upgrade

  • Recreate SSO connections: create each organization’s SAML connection under Settings → SSO, and have the identity provider administrator update the Kindo app to match. Then remove SSOReady and its hostnames.
  • Switch sandboxes to OpenShell: upgrades keep your current sandbox provider. Switch the SANDBOX_PROVIDER flag to OpenShell; it is the supported provider for self-managed installs.
  • Persistent workspaces are generally available: they need OpenShell. Upgrades keep your existing PERSISTENT_SANDBOX_WORKSPACES setting, so after switching to OpenShell, enable the flag in Unleash if it is off. Each workspace keeps its own volume, 10 Gi by default, so monitor sandbox storage.

Good to know

  • Background-task history is now kept for 7 days.
  • Each PII analyzer pod now reserves 2.5 CPU and 4 GiB, so make sure your nodes have room.

Removed

  • Removed: models in the install contract. Models you registered on 2026.07 carry over; manage models in the superadmin dashboard.
  • Removed: the kindo model list and kindo sso commands. Use the superadmin dashboard and Settings → SSO instead.
  • Removed: MCP Prompts, in chat and through the /v1/mcp gateway. Tools and resources are unaffected.
  • Removed: the separate model proxy hostname. Call the API host with a Kindo API key instead.

Updates

Latest

2026.09.14

  • Agents reading a sandbox file now get its last line when the file has no trailing line break.
  • Organization admins can now search every agent in the organization from the usage statistics agent filter.
  • Integrations no longer write temporary file-access links to their logs or traces.
  • File uploads to GitHub and SharePoint now use the same download safeguards as other integrations.

Early access

Early-access integrations have not yet been validated against a production deployment. Operators enable them like any other integration, using the name in parentheses.

  • SQL Database (sql-database, early access): agents can now run a SQL file from the sandbox in one transaction, on connections that allow writes.

2026.09.12

  • Fixed SAML SSO sign-in, which failed with an internal server error after upgrading to 2026.09.11.

2026.09.11

  • Changed default: Telemetry field names have changed — update custom dashboards, searches, and alerts.
  • Changed default: Sandbox workloads now schedule onto the configured sandbox node pool.
  • Removed: Trust for eight compromised certificate authorities, across all shipped images.
  • Scheduled agents no longer run an hour off around daylight-saving changes.
  • New integration connections now register reliably on self-managed installs.
  • Upgrades now reapply integration webhook setup, so existing connections keep working.
  • Fixed credential refresh for SharePoint and OneDrive connections.
  • Session lifetime can now be set in minutes, not only whole hours.
  • API keys and file download links are no longer written to logs.
  • Database usernames and hosts are no longer included in telemetry.
  • Deleting an SSO connection now also removes its linked sign-in records.
  • Linking a new sign-in method now respects an organization’s SSO requirement.
  • Pressing Back after signing out no longer shows the previous page.
  • Organization invite links no longer pass their identifier to third-party analytics.
  • Updated the authentication library to its latest patch; no database migration required.
  • Rebuilt sandbox and service images with patched system libraries and runtimes.
  • Oversized request payloads are now rejected before processing.
  • Applied security updates across bundled platform and integration dependencies.

2026.09.10

  • Fixed a 2026.09.9 regression that made Microsoft integrations stop working once their saved access expired. Two integrations, SharePoint Online and OneDrive, are still affected; see the known issue below. If another Microsoft integration still fails after this upgrade, reconnect it.
  • Known issue: SharePoint Online and OneDrive connections cannot renew their access on 2026.09.9 and 2026.09.10, with single-tenant and multi-tenant app registrations alike. SharePoint Online (Application) is not affected. Reconnecting restores a connection only until its access next expires, and there is no other workaround. Upgrading from 2026.09.8 or earlier introduces this; if you rely on these integrations and run 2026.09.8 or earlier, stay on that release until a later release fixes it.

2026.09.9

  • Action for single-tenant Microsoft app registrations: Microsoft integrations can now sign users in at your own Microsoft tenant. If your app registration is single-tenant, run kindo config helm-override set api envData.MICROSOFT_DELEGATED_SIGN_IN=per-connection, then kindo config helm-override apply api; users then enter their Microsoft domain or tenant ID when they connect. Multi-tenant registrations need no change.
  • Fixed a blank page in the web app after upgrading to 2026.09.8.

2026.09.7

  • Applying configuration changes now updates running services, so settings such as syslog forwarding take effect.

2026.09.6

  • Fixed sandbox tools becoming unavailable as gateway memory grew over time.
  • Saving model pricing or adopting a deployment no longer breaks its stored credentials.
  • Fixed Obsidian Security connections failing on every request.
  • Connections to third-party services now send only the credential they need.
  • Updated trusted certificate roots and runtime dependencies for published security advisories.
  • Audit events can now be forwarded to a syslog receiver over UDP, TCP, or TLS.
  • Fixed a self-managed upgrade failure caused by the monitoring setup step.
  • Upgrades now set the in-cluster storage URL as part of the upgrade run.
  • Deployment docs now recommend ingress header buffer sizing to avoid intermittent login errors.

2026.09.5

  • Fixed an upgrade check that wrongly blocked upgrades from older releases.
  • Fixed failing filter lookups in the Tenable Vulnerability Management integration.

2026.09.4

  • Outlook can read the files in a zip attachment or in an attached message. The maximum attachment size for reading is now 50 MB (it was approximately 26 MB).
  • Outlook can save an attachment to the Kindo library, find mail sent outside your organization, and move a message to a different folder. To move messages, add the Mail.ReadWrite permission. To find external mail on an application connection, add Organization.Read.All.
  • Outlook can find a message by its Internet message ID.
  • Microsoft Graph Security can quarantine, move, or permanently delete an email that Defender analyzed. This works only on application connections in the commercial cloud. Add the SecurityAnalyzedMessage.ReadWrite.All permission and grant admin consent.
  • Microsoft Entra ID can revoke all sign-in sessions of a user. Add the User.RevokeSessions.All permission and grant admin consent.

2026.09.3

  • Fixed SAML single sign-on setup failures with AD FS for new connections.
  • Microsoft connections now accept a verified domain instead of the tenant ID.
  • SharePoint tools now target a chosen site, which can be found from its URL.

2026.09.2

  • Services that start before the feature-flag service no longer lose flags permanently.
  • Fixed install failures when adopting a newer existing External Secrets Operator.
  • Adopting a self-hosted gateway model now lets you set its context window.

2026.09.1

  • Removed: Upgrade no longer rebuilds missing configuration files, and kindo upgrade --reconstruct is gone. Run the upgrade from your install directory, or pass --contract and --bindings. If the files are lost, contact Kindo support.
  • Changed default: Upgrade now sends a test email to the operator address during preflight. Pass --no-test-email to skip it.
  • Upgrades are more reliable and safer for existing installs.
  • Upgrade plans now stop when a published service URL would change.
  • Self-managed installs can now use SMTP relays that require no authentication.
  • New Outlook application connection for tenant-wide mailbox access.
  • Agents can now read email attachment contents, not just file names.