Skip to main content
For the complete documentation index for agents and LLMs, see llms.txt.

Release 2026.5

Check what's coming in May.

Builder Updates​

Semantic Search in Builder​

Search for components in Builder using natural language queries. This is a powerful feature that helps you find the right components for your pipeline quickly and easily. To find a component:

  1. In Builder, open the Component Library.
  2. Type your query in the search bar using natural language. For example, "generate text from documents" or "rank search results by relevance". The library will suggest components that match your query.

For details, see Create a Pipeline in Builder.

Improved File Preview in Playground​

Uploaded file previews in Playground now work correctly for all supported file types. Image files (PNG, JPG, JPEG, GIF, WebP, SVG) now display inline as images instead of being treated as binary content. Other file types also benefit from improved MIME type detection, so PDFs, text files, and other formats render reliably after upload.

For details on supported preview formats, see Upload Files.

Organizing Components with Groups​

Group components to organize them and make your pipelines more readable. Groups help you keep related components together and you can collapse them to reduce visual clutter.

To create a group, click the Groups button (group icon) in the bottom right corner of the canvas. Then click and drag on the canvas to draw a rectangle around the components you want to group.

Keyboard shortcut: Press Cmd+G (Mac) or Ctrl+G (Windows/Linux) to activate group drawing mode, then draw the rectangle. Press Esc to cancel drawing mode.

Groups are saved with your pipeline and restored when you reload the builder.

The Builder canvas with a group rectangle drawn around the components

Updated Editor Role​

The Editor role can now manage workspace members, including adding and removing them, and updating their roles. For details, see User Roles and Permissions.

Simpler Pipeline Versions​

Creating a new draft version no longer fails when a draft already exists. If you create a new draft and one already exists, the existing draft is automatically finalized and a new draft is created in its place. You only see a conflict error if another user is actively editing the existing draft. For details, see Manage Pipeline Versions.