NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
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.
Backport: wake kinm watches with LISTEN/NOTIFY and refresh them on promotion (#7736) by @cjellick in https://github.com/obot-platform/obot/pull/7763
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.5-rc3...v0.25.5-rc4
Hold the controller leader lock in a SQL table instead of a Lease - https://github.com/obot-platform/obot/pull/7727
Hold the controller leader lock in a SQL table instead of a Lease - https://github.com/obot-platform/obot/pull/7727
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.5-rc2...v0.25.5-rc3
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.5-rc1...v0.25.5-rc2
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.5-rc1...v0.25.5-rc2
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.4...v0.25.5-rc1
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.4...v0.25.5-rc1
This is a hotfix that fixes some bugs when running Obot with more than one replica.
This is a hotfix that fixes some bugs when running Obot with more than one replica.
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.3...v0.25.4
This is a small patch release to add a preconfigure option in the MCP Connect modal - #7678
This is a small patch release to add a preconfigure option in the MCP Connect modal - #7678
"I've been asking for this since we removed it." - @thedadams
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.2...v0.25.3
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.3-rc2...v0.25.3-rc3
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.3-rc2...v0.25.3-rc3
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.3-rc1...v0.25.3-rc2
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.3-rc1...v0.25.3-rc2
2a45a2ca1680c5ee1d871a5c283c31ed09dde2fa enhance: add preconfigure option for entry in MCP Servers
This is a patch release to fix an issue for auth providers with over 100 groups.
This is a patch release to fix an issue for auth providers with over 100 groups.
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.1...v0.25.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
enhance: add configuration to force DCR by @thedadams in https://github.com/obot-platform/obot/pull/7438
Full Changelog: https://github.com/obot-platform/obot/compare/v0.25.0...v0.25.1
Nothing published for this version
chore: update vulnerable dependencies by @calvinmclean in https://github.com/obot-platform/obot/pull/7261
We're excited to announce the v0.25.0 release of the Obot Platform. This release adds tool call enforcement for local AI clients, MCP tunnels for reaching MCP servers on private networks, Agent Auth Scopes, and a new set of Obot editions.
Obot can now control which tool calls Claude Code, Codex, and Cursor are allowed to run on enrolled devices. Administrators define an allowlist as part of device management and Obot Sentry checks each tool call against it before the client runs the tool. A call runs only when an allow rule matches it.
A rule can cover a broad category, such as all Obot-hosted MCP servers or all built-in agent tools, or it can name a single MCP server by URL, hostname, npm or PyPI package, or connector display name. Enforcement fails closed, so Obot Sentry blocks any call it cannot match or cannot get a decision on. A new Enforcement Decisions view under Device Management records every call that was checked and shows why it was allowed or blocked.
Note: Tool call enforcement is experimental and is not yet recommended for production use, so test your allowlist on non-production devices first. Enforcement is also not supported for Visual Studio Code, because its pre-tool hook does not say which MCP server a tool belongs to. Local tool call auditing for Visual Studio Code continues to work. See #7425 for details.
See the docs for details.
Obot can now reach remote MCP servers that run on a private network and are not routable from the Obot deployment. An obot tunnel process runs on a machine that can reach both Obot and the private MCP server, and it opens an outbound, authenticated WebSocket connection that Obot sends requests through. The machine running the tunnel does not need an inbound port.
Tunnels are especially useful if you use Obot Cloud, where we run Obot for you and it sits outside your network. You run the tunnel process inside your network, and you do not have to expose the server to the internet or open a port in your firewall.
Administrators create a tunnel under MCP Management > MCP Tunnels, and each tunnel carries a list of allowed URLs that Obot checks on every request. A remote MCP catalog entry then selects the tunnel by its ID. Tunnels also work across replicas.
See the docs for details.
We reworked how you set up access for an autonomous or headless agent, so you can grant an agent only what it needs to do its job. What used to be called API keys are now called Agent Auth Scopes, and the change is the start of a larger effort to extend Obot's authorization model to more agentic workloads. You create a scope and Obot generates an API key that the agent uses instead of signing in through a browser.
A scope can be limited to specific MCP servers or to every server you can reach. On top of that, it can grant access to the Obot API, the LLM proxy, skill downloads, and device scans, and it can carry an expiration date.
The interface moved to match. Users now reach scopes from the top level of the Obot app navigation, and administrators reach them under Auth Management, which was previously called User Management.
See the docs for details.
Obot is now available in three editions. You can upgrade from one to the next inside the app without changing images or redeploying. The default Obot edition supports up to 100 users and 100 devices, with the GitHub, Google, and Local auth providers. Obot Community keeps the same limits and adds enterprise-grade auth providers such as Entra, Okta, JumpCloud, and Auth0. Obot Enterprise removes the limits and includes enterprise support.
See the docs for details and read the Upgrade Notes below before you upgrade.
Obot end user licensing has changed. Starting with v0.25.0, Obot is offered in three editions, which are Obot, Obot Community, and Obot Enterprise. The code remains 100 percent MIT licensed, and parts that were previously closed source, including the enterprise auth providers and model providers, are now open source. Before you upgrade, check how the change affects your deployment:
Tool call enforcement is not supported for Visual Studio Code. Claude Code, Codex, and Cursor support enforcement. Visual Studio Code does not, because its pre-tool hook does not say which MCP server a tool belongs to. Local tool call auditing for Visual Studio Code continues to work. See #7425 for details.
Full Changelog: https://github.com/obot-platform/obot/compare/v0.24.1...v0.25.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
chore: update vulnerable dependencies by @calvinmclean in https://github.com/obot-platform/obot/pull/7261
Full Changelog: https://github.com/obot-platform/obot/compare/v0.24.1...v0.25.0-rc1
Full Changelog: https://github.com/obot-platform/obot/compare/v0.24.1...v0.24.2
Full Changelog: https://github.com/obot-platform/obot/compare/v0.24.1...v0.24.2
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
fix: allow creating MCP servers without URL during setup by @thedadams in https://github.com/obot-platform/obot/pull/7299
Full Changelog: https://github.com/obot-platform/obot/compare/v0.24.0...v0.24.1
Nothing published for this version
Nothing published for this version
Deprecated catalog entries now show a notice in the catalog, connect, and server-management views.
We're excited to announce the v0.24.0 release of the Obot Platform. This release expands Device Management with AI client audit logging and MDM support, brings full audit logging to the LLM Gateway, and adds AWS Bedrock and Azure support to the LLM Gateway. It also reworks Obot's MCP proxy to substantially reduce its resource footprint.
Obot's Device Management feature expands this release, built around a new companion tool called Obot Sentry. Administrators can define an MDM configuration, issue enrollment keys, and generate per-platform install packages so devices enroll themselves. Enrolled devices authenticate with device-bound keys and submit scans over short-lived signed tokens.
Once installed, either manually or pushed through an MDM, Obot Sentry does two things: it submits periodic device scans, and it installs managed hooks for supported local AI coding tools, currently Claude Code, Codex, Visual Studio Code, and Cursor. Every tool call those tools make is submitted back to Obot and recorded in the MCP Audit Logs, normalized into the same event schema as MCP tool calls so the two appear side by side. See the Upgrade Notes below if you export audit logs today, as the exported format has changed.
We are initially shipping with first-class support for Microsoft Intune, and plan to add other MDM providers such as Jamf in future releases.
Device Management, including MDM enrollment, remains in Beta, and the
obot scanCLI command has been removed in favor of Obot Sentry-based scanning. See #7249 for details.
See the docs for details.
Obot now keeps a full audit trail of LLM Gateway activity. Every request that flows through the gateway is logged with its model, provider, user-agent, token usage, and outcome, and users with the Auditor role can view full request and response bodies. A new Audit Logs page under LLM Gateway supports filtering by provider, model, request path, status, user-agent, and session, along with one-time and scheduled export to S3, GCS, or Azure.
See the docs for details.
The LLM Gateway adds three new provider options this release. AWS Bedrock can be configured with either static IAM credentials or a Bedrock API key, and routes Anthropic, OpenAI, and Google model families hosted on Bedrock through AWS inference profiles. Azure can be configured with an API key or an Entra ID service principal, covering both Azure OpenAI and Microsoft Foundry deployments. The Generic Responses provider, now out of experimental, lets Obot call any OpenAI Responses API compatible endpoint such as Ollama or LiteLLM.
If you were already using the previous Bedrock provider, you may need to update your API keys and reselect models, since credentials are scoped differently under the new provider. See the docs for setup details.
Composite MCP catalog entries can now be defined through the Git-backed MCP catalog like any other server type. Component servers are referenced by a stable entry key instead of an internal catalog-entry ID, so a composite entry can reference components from its own catalog source or from a different one entirely.
Obot's MCP proxy has been rewritten this release. Previously, remote and composite MCP servers were fronted by a distributed proxy, meaning every remote or composite server required its own Kubernetes pod or Docker container just to proxy traffic to it, consuming significant additional resources across a deployment. That proxy has now been moved entirely into the main Obot server process.
The result is a substantially smaller footprint: Obot now only deploys a pod or container when you choose to actually host an MCP server yourself (via the npx, uvx, or containerized runtimes), rather than for every remote or composite server it fronts.
See the Upgrade Notes below if you run Obot with the Docker backend.
Obot now includes a built-in local authentication provider backed by its own database, so users can get up and running quickly when trying out Obot instead of spending time to integrate with an OAuth provider. It's aimed at development and testing and is not suited for production deployments.
Administrators enable the Local provider from Admin > Auth Providers, restrict it to specific email domains (or allow any), and create user accounts from a "Manage Users" dialog, which also handles password resets. Local users cannot change their own password; an admin must reset it, which signs the user out of all existing sessions. Passwords are hashed with Argon2id and are never stored or returned in plaintext.
Local authentication is intended for development and testing, not for production use.
See the docs for setup details.
Obot now includes an in-app guided tour that highlights real interface elements and steps users through common tasks, replacing an older static tour. Separate guide tracks are available for end users, covering connecting to an MCP server and installing skills or the CLI, and for administrators, covering catalog entry creation and MCP access policies.
Guides can be hidden or re-enabled from the profile menu under My Account.
This release contains several behavior changes and known issues. Review carefully before upgrading.
Helm chart configuration overhaul. Kubernetes installations now separate sensitive settings into a Secret and non-sensitive settings into a ConfigMap. Update your custom values before upgrading:
config.existingSecret to secret.existingSecret.config.* to secret.*, including database DSNs, API keys, encryption keys, bootstrap tokens, license keys, and artifact-storage credentials. Known sensitive values left under config now cause chart rendering to fail.secret.existingSecret with mcpImagePullSecrets, provide OBOT_SERVER_MCPIMAGE_PULL_SECRETS in the external Secret.OBOT_SERVER_MCPBASE_IMAGE no longer receives an automatic chart-version tag, so configure an explicit image tag if you relied on that behavior.Additional Helm changes in this release:
persistence.storageClass to "-" explicitly disables dynamic storage-class selection.See #7252 for details.
obot scan CLI command removed. Device scanning now happens through Obot Sentry, installed manually or via MDM, instead of the CLI. If you have scripts or automation calling obot scan, they will need to move to Obot Sentry instead. See #7249 for details.
Audit log export format has changed. The JSON shape of exported audit logs (S3, GCS, or Azure) has changed completely, replacing the old flat per-log-type shape with a single normalized event envelope shared by MCP and local-agent tool-call events. Anything consuming exported logs downstream will need to be updated to the new shape. See #7174 for details.
Old Slack MCP server deprecated. The original Slack MCP server in Obot's default catalog is now marked deprecated in favor of a new official Slack MCP server. There is no automatic migration; existing users should switch manually. The legacy Slack server will be removed completely by the end of August 2026. See #7173 for details.
Docker-mode users should clean up old shim containers. As part of the MCP proxy rework above, Kubernetes deployments clean up old shim containers automatically, but Docker-mode deployments will not remove them on their own. Remove them with:
docker ps -aq --filter "label=mcp.deployment.id" | xargs docker rm -f
Known issue with Obot Sentry: macOS manual installs create multiple device identities. When Obot Sentry is installed using the macOS standalone binary instructions, audit hooks can use a different device identity from device scans. As a result, hook audit logs and inventory scans appear under different device IDs. See #7298 (https://github.com/obot-platform/obot/issues/7298) for status and updates.
Behavior Change: Basic users no longer see audit logs or usage for their MCP servers. We found this confused basic users and didn't add much to their experience.
See #7100 for details.
Full Changelog: https://github.com/obot-platform/obot/compare/v0.23.1...v0.24.0
fix: bump kinm by @thedadams in https://github.com/obot-platform/obot/pull/7156
Full Changelog: https://github.com/obot-platform/obot/compare/v0.23.3...v0.23.4
fix: bump kinm by @thedadams in https://github.com/obot-platform/obot/pull/7156
Full Changelog: https://github.com/obot-platform/obot/compare/v0.23.3...v0.23.4-rc1
chore: bump nanobot to pick up extra logging by @thedadams in https://github.com/obot-platform/obot/pull/7049
Full Changelog: https://github.com/obot-platform/obot/compare/v0.23.2...v0.23.3
This is a patch release to address a rate-limiting issue with our licensing provider.
This is a patch release to address a rate-limiting issue with our licensing provider.
As part of this patch release, we’re also publishing 3 security advisories. These were fixed in the v0.23.0 release, so you’re only affected if you’re on a release less than or equal to v0.22.1.
Full Changelog: https://github.com/obot-platform/obot/compare/v0.23.1...v0.23.2
One column per month.