NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1690 by repository stars
Latest stable
v0.28.0
Last release 13 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 58 of 58 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
3023 releases · first in 2024
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Embedded PostgreSQL moves from 17 to 18. This is a breaking change for installations using the embedded database: Docker without OBOT_SERVER_DSN, and…
We're excited to announce the v0.28.0 release of the Obot Platform. This release introduces a unified LLM gateway with profiles, budgets, and guardrails, publishes vMCPs through the MCP Registry API, adds Keycloak and OneLogin auth providers with SCIM provisioning for Entra and OneLogin, and lets remote and containerized MCP servers receive trusted caller attribution headers.
Obot now reaches every model through one LLM gateway. A single endpoint, /api/llm-proxy, serves every configured model in the OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages formats, so Claude Code can use GPT models and the OpenAI SDK can use Claude. Administrators manage providers, keys, routing rules, weighted splits, and fallbacks from the LLM Gateway page, and the Connect tab gives ready-to-copy setup for Claude Code, Codex, OpenCode, Goose, Cline, Open WebUI, and the common SDKs. Bedrock and Azure providers support each of their authentication methods, and all providers' configuration is stored in Obot's own database.
Model access policies are now profiles. Each profile names users and groups, the models they can use, budgets that cap spend, tokens, or requests over rolling or calendar windows, and applied guardrails. Guardrails include built-in secrets, regex/PII, and LLM judge checks, along with integrations for Presidio, Azure AI Language and Content Safety, AWS Bedrock Guardrails, Google Model Armor, Lakera Guard (Check Point), Patronus, and CrowdStrike AIDR. They block, redact, or log model traffic, including streamed responses, and guardrail filters apply the same checks to MCP tool calls. Administrators can also let Claude Code users bill requests to their own Claude subscription while Obot still enforces access and guardrails and records each request in the audit log. See the docs for details.
[!IMPORTANT] Existing LLM gateway and model provider users should wait to upgrade. Provider credentials, models, default model aliases, and model access policies are not migrated to the new gateway in v0.28.0. Migration support is planned for v0.28.1. See #8475 for details.
The MCP Registry API now publishes vMCPs with their connection URLs. What each user discovers follows vMCP ownership and profile access, and authenticated discovery returns a personalized view.
Administrators can enable anonymous discovery under Platform → Settings → MCP Registry API for clients that don't authenticate registry requests, such as VS Code. Anonymous requests see only shared vMCPs whose profiles grant access to All Obot Users, and connecting still requires authentication and current vMCP permissions. See the docs for details.
Keycloak and OneLogin are now available as authentication providers. See the docs for setup.
Microsoft Entra and OneLogin can now provision users and groups into Obot through SCIM, as Okta could in v0.27.0. Administrators decide in their identity provider which users and groups Obot can see, and users removed there are deactivated in Obot. See the docs for Entra SCIM and OneLogin SCIM.
Remote and containerized MCP servers and their catalog entries can now receive trusted X-Obot-* headers that identify the caller: the Obot user ID, name, and email, the identity provider user ID and groups, and the API key ID and name. Each header is selected individually under Advanced Configuration → Inject Obot headers.
Obot strips any incoming copies of these headers before forwarding a request, so a backend can attribute actions to a user or enforce per-caller policy without trusting client input. See the docs for details.
Existing LLM gateway and model provider users should wait to upgrade. v0.28.0 does not migrate existing provider credentials, models, default model aliases, or model access policies to the new LLM gateway. Migration support is planned for v0.28.1 and tracked in #8474. Earlier gateway data is not changed, and LLM audit history stays readable. The per-provider proxy routes for Amazon Bedrock, Azure OpenAI, and Generic Responses (/api/llm-proxy/aws-bedrock, aws-bedrock-api-key, azure, azure-entra, and generic-responses) are temporarily unavailable and return HTTP 410. They will be restored, see #8495. /api/llm-proxy/openai and /api/llm-proxy/anthropic still work. See #8475 for details.
Message policies are now disabled LLM judge guardrails. Message policies are converted into LLM judge guardrails on upgrade, and every converted rule starts disabled. OBOT_SERVER_ENABLE_MESSAGE_POLICIES is removed. If you enforced message policies, review and enable the converted rules under LLM Gateway → Profiles. Enabled rules fail closed when the judge's model is unavailable. See #8302 for details.
Anonymous MCP Registry API discovery is now opt-in. Anonymous discovery is disabled by default. OBOT_SERVER_ENABLE_REGISTRY_AUTH no longer has any effect, and its value is not imported. If clients such as VS Code discover servers without authenticating, enable Allow anonymous registry discovery under Platform → Settings → MCP Registry API after upgrading. See #8310 for details.
Obot attribution headers are reserved. The seven X-Obot-* attribution headers can no longer be configured manually on MCP servers, and configurations that set them may fail validation. Before upgrading, remove them and use Advanced Configuration → Inject Obot headers instead. See #8402 for details.
Owner and admin email environment variables are removed. OBOT_SERVER_AUTH_OWNER_EMAILS and OBOT_SERVER_AUTH_ADMIN_EMAILS are removed. Users who were granted roles by them keep those roles, but those roles can now be changed on the Users page. See #8440 for details.
The users.verified_email database column is dropped. During a rolling upgrade, v0.27 pods can return errors to users until the rollout finishes. See #8482 for details.
Embedded PostgreSQL moves from 17 to 18. This is a breaking change for installations using the embedded database: Docker without OBOT_SERVER_DSN, and Helm with dev.useEmbeddedDb: true. Obot stops at startup on a PostgreSQL 17 data directory. Follow the dump and restore guide before upgrading. Installations using external PostgreSQL are not affected. See #8439 for details.
Full Changelog: https://github.com/obot-platform/obot/compare/v0.27.0...v0.28.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
test(ui): stop forced click from skipping audit log export submit by @thedadams in https://github.com/obot-platform/obot/pull/8364
Full Changelog: https://github.com/obot-platform/obot/compare/v0.28.0-alpha3...v0.28.0-rc1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
enhance: add view audit logs option in environment sessions by @ivyjeong13 in https://github.com/obot-platform/obot/pull/8360
Full Changelog: https://github.com/obot-platform/obot/compare/v0.28.0-alpha2...v0.28.0-alpha3
Nothing published for this version
Nothing published for this version
fix(claude): disable upstream TLS session resumption in the egress proxy by @cjellick in https://github.com/obot-platform/obot/pull/8358
Full Changelog: https://github.com/obot-platform/obot/compare/v0.28.0-alpha1...v0.28.0-alpha2
Nothing published for this version
chore: fix winget release and allow publishing manually by @njhale in https://github.com/obot-platform/obot/pull/8337
Full Changelog: https://github.com/obot-platform/obot/compare/v0.27.0...v0.28.0-alpha1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
docs: add a threat model and tighten the vulnerability reporting policy by @cjellick in https://github.com/obot-platform/obot/pull/8161
We're excited to announce the v0.27.0 release of the Obot Platform. This release adds experimental Claude Environments for running Claude sessions on your own Kubernetes infrastructure, OpenAPI-backed MCP servers, Okta SCIM provisioning, a localized UI, and tool search for vMCPs.
Organizations can now run Claude cloud sessions on their own Kubernetes infrastructure. Users keep working in Claude, while Obot decides who can start a session, which vMCPs the session can use, where it can send network traffic, and how much CPU and memory it gets. Obot uses Agent Substrate to run isolated sessions and suspend idle workspaces. Claude Environments replaces the former Hosted Agents feature.
Administrators create an environment from a Claude environment key, then grant access through profiles that map users and groups to vMCPs, resource limits, and egress rules. Session traffic is limited to allowed hosts, and destination-specific secrets are injected at the egress gateway, so the session never sees them. Obot vMCP credentials are scoped to the mapped Obot user, and every egress request is recorded in Audit Logs. Administrators map Claude organization members to Obot users, and Claude Tag sessions started from Slack or GitHub run under a dedicated service identity. See the docs for cluster requirements and setup.
[!IMPORTANT] Claude Environments is experimental and disabled by default. It uses new technology, requires Obot to run in Kubernetes, and needs additional cluster resources and configuration. It also requires a Claude Team or Enterprise organization with self-hosted environments enabled. See #8276 for details.
Obot can now host an MCP server for any HTTP API that has an OpenAPI schema, without anyone writing a separate MCP server. Administrators import a schema from a URL or a file, and Obot pre-fills the name, description, API destination, and credential headers for review before saving. Each API operation becomes an MCP tool.
OpenAPI servers run on Docker or Kubernetes from a saved snapshot of the schema, and MCP egress policies apply to them. API keys and bearer tokens are forwarded on each request. OpenAPI entries are also supported in Git-backed catalogs, and existing servers keep their schema snapshot until they are explicitly upgraded. See the docs for details.
[!NOTE] OpenAPI-backed MCP servers support header API keys and pre-issued bearer tokens, but do not perform OAuth flows against the upstream API. OAuth declarations in a schema are imported but do not configure authentication. Schemas are limited to 1 MiB. See #8253 and #8250 for details.
Okta can now provision users, groups, and group memberships into Obot through SCIM. Administrators decide in Okta which users and groups Obot can see, and Obot no longer needs read access to the Okta directory. Users still sign in through the existing Okta OIDC app.
Removing a user's assignment in Okta now deactivates them in Obot. They are signed out, and their API keys and other credentials stop working. When configuring the Okta auth provider, administrators choose between SCIM and the Okta API for group data. See the docs for setup.
The Obot UI is now available in Japanese, Korean, and Simplified Chinese in addition to English. The language defaults to the browser's language and can be changed from the profile menu. Auth and model provider configuration text returned by the API is localized as well.
vMCPs have a new opt-in Tool search setting. When it is enabled, clients see two tools, search_tools and call_tool, instead of the full tool list, which keeps tool definitions out of the model's context when a vMCP has many tools. Obot recommends enabling it for vMCPs with more than 50 tools.
Tool search does not grant additional access. The same component, profile, and user selections determine which tools can be found and called, and each call is validated, authorized, and audited as the underlying tool. The setting is also supported in catalog YAML. See the docs for details.
obot mcp login <url>.minObotVersion and maxObotVersion to limit which Obot versions offer them.Obot Agent has been removed. Obot Agent has been disabled by default since v0.23.0 and is removed in this release. Claude Environments is the planned replacement. The OBOT_ENABLE_AGENTS setting and the User Impersonation role are removed with it, and containerized MCP servers redeploy once after the upgrade. See #8274 for details. If you were using this feature, we recommend you don't upgrade to v0.27. But please reach out and let us know what you'd like to see as a replacement.
Hosted Agents has been removed. Hosted Agents was off by default and never left experimental status. It has been removed and replaced by Claude Environments, and its resources are cleaned up on upgrade. See #8275 for details. If you were using this feature, we recommend you don't upgrade to v0.27. Claude Environments is a partial replacement, but doesn't cover all use cases. But please reach out and let us know what you'd like to see as a replacement.
MCP clients must connect through vMCPs. Direct connections to catalog entries, MCP servers, and server instances are now rejected. Connections that were migrated to vMCPs keep their existing URLs. See #8178 for details.
Several default catalog entries are deprecated. Legacy Slack is scheduled for removal on October 30, 2026. AntV Charts, Brave Search, Browserbase, Chroma Cloud, MarkItDown, Playwright, and MongoDB Atlas Management will also be removed, on dates not yet announced. Upgrade to at least v0.26.2 before these entries are removed so existing deployments are preserved. See #8269 for recommended replacements.
Full Changelog: https://github.com/obot-platform/obot/compare/v0.26.2...v0.27.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
fix: stop compiling claude runner on Windows by @thedadams in https://github.com/obot-platform/obot/pull/8329
Full Changelog: https://github.com/obot-platform/obot/compare/v0.27.0-rc1...v0.27.0-rc2
One column per month.