Last updated: August 23, 2026
How we publish updates
The changelog lists product-visible changes to Studio, workspace governance, governed requests, the Python SDK, and public APIs—curated for operators and developers integrating Kimss.
Entries below load from the published changelog API. Draft notes and internal-only changes never appear here. For architectural context behind major releases, read /docs/architecture and /insights.
What to watch
Breaking API changes, new /v1 capabilities, governed-request policy adjustments, and SDK releases affect integration timelines—scan tags and summaries before upgrading production workspaces.
Pair changelog reading with /assistants-to-v1-migration when deprecations touch legacy assistant routes. Enterprise customers can request briefings via /enterprise.
Release categories
Entries may cover Studio UX, workspace admin, governed requests, Python SDK packages, MCP tools, public /v1 APIs, and infrastructure notes that change how you operate the control plane.
SDK releases often require coordinated client upgrades—check tags on each entry before bumping dependencies in CI. API changes reference /docs/api_docs as the integration contract.
Governance-related releases may adjust governed-request defaults, RBAC surfaces, or Entra SSO flows; platform teams should read those entries before announcing allowance changes to product squads.
Subscribe to /insights for longer engineering narratives that complement short changelog summaries.
Published entries
Released changes appear automatically from the public changelog API—newest entries first, with dates, summaries, and tags for SDK, API, and governance work.
Loading published updates…