github obot-platform/obot v0.18.0
on GitHub

latest releases: v0.23.3, v0.23.2, v0.23.2-rc1...
3 months ago

We’re excited to announce the v0.18.0 release of the Obot MCP Platform. This release introduces workflow sharing for Obot Agent, adds first-class skills management with governed access policies, and expands enterprise identity support with Auth0 integration. It also delivers major improvements across agent usability, observability, and runtime performance.

Big Updates

Workflow Sharing

This release introduces Workflow Sharing for Obot Agent.

Users can now publish complete workflows from Obot Agent so they can be discovered and installed by other users as reusable starting points. Published workflows are versioned per user and workflow name, include the full workflow directory, and can be kept private or made public through the UI.

This gives teams a practical way to standardize and distribute repeatable agent workflows without relying on manual copying or ad hoc file sharing.

Behind the scenes, Obot now supports dedicated storage for published workflow artifacts, with support for local disk, S3-compatible storage, GCS, and Azure Blob depending on your deployment model.

Skills and Skill Access Policies

This release adds first-class Skills support to Obot.

Administrators can now register GitHub-based skill repositories, scan them for valid SKILL.md packages, browse discovered skills in the UI, and refresh repositories as needed. Agents can then search for and install those skills directly during conversations.

For a reference set of curated skills, see the obot-platform/skills repository.

To govern rollout, Obot now includes Skill Access Policies. These policies let administrators grant access to all skills, entire repositories, or individual skills for specific users, groups, or all users.

This provides a controlled way to expand agent capabilities across the organization while keeping skill availability aligned with governance and team boundaries.

Auth0 Enterprise Authentication

Obot now supports Auth0 as an enterprise authentication provider.

Organizations using Auth0 can now integrate Obot into their existing identity stack, with support for Auth0-specific provider configuration, user identity handling, and Management API-backed user and role resolution.

This makes enterprise rollout easier for teams already standardized on Auth0 and improves compatibility with policy-driven access control inside Obot.

Embedded Browser Viewer for Obot Agent

Launched Obot Agents can now expose their browser session directly inside the Obot UI.

The new embedded browser viewer gives users a live view into browser-based agent activity without leaving Obot, making web-driven agent workflows easier to monitor and guide. The UI also now hides browser controls until a browser session is actually available, improving clarity during agent startup.

Upgrade Notes

This release changes the workflow spec used by Obot Agent to align with the agentskills.io format. If you have existing workflows created before v0.18.0, they require a one-time migration after upgrading so they match the new spec.

After upgrading to v0.18.0, open your Obot Agent and give it the following prompt: 

Refactor all of my existing workflows to match the agentskills.io spec. Here's what needs to happen:

For each markdown file in the workflows/ directory that is NOT already in the proper format (i.e., it's a loose .md file rather than a <name>/SKILL.md directory):

1. **Read** the old file and understand what the workflow does.

2. **Create the new directory structure**: Convert the filename to a valid slug (lowercase, hyphens only, no leading/trailing/consecutive hyphens, max 64 chars). Create `workflows/<slug>/SKILL.md`.

3. **Add proper YAML frontmatter** with:
   - `name`: the slug (must match directory name exactly)
   - `description`: a concise description of what the workflow does (max 1024 chars), inferred from the content
   - `metadata.createdAt`: use `date -u +"%Y-%m-%dT%H:%M:%SZ"` to get the current UTC time

4. **Restructure the body** into the standard sections:
   - `## Inputs` — extract any parameters/variables the workflow expects. Format each as `- **param_name** (required/optional): Description. Default: value`
   - `## Steps` — number each step as `### 1. Step Name` with descriptive title-case names. Preserve the original intent and instructions of each step. Use `{{input.name}}` to reference inputs and `{{Step Name}}` to reference outputs of prior steps.
   - `## Output` — if the workflow has a clear final output format, add this section using `{{Step Name}}` variables to compose the result.

5. **Preserve any supporting files** (scripts, data files, etc.) by moving them into the new directory alongside SKILL.md.

6. **Add conditions and error handling** where appropriate:
   - If a step has conditional logic, add `**Condition:** {{Step Name}} contains X`
   - If a step could fail and has recovery logic, add `**On error:** stop|continue|Step Name`

7. **Delete the old .md file** after successfully creating the new SKILL.md.

Before making any changes, list all workflows you found and show me what each will look like after refactoring. Wait for my approval before writing any files.

Do NOT change the actual behavior or intent of any workflow — this is a format migration only. If a workflow is ambiguous or you're unsure how to structure it, ask me.

What's Changed

Full Changelog: v0.17.1...v0.18.0

Check out latest releases or
releases around obot-platform/obot v0.18.0

Don't miss a new obot release

NewReleases is sending notifications on new releases.

Get notifications