Assistants are now Agents

We're renaming Assistants to Agents across Langdock! This change reflects how the product has evolved and how the market and many of you talk about AI.

What's changing?

Only the name. Your existing assistants keep all their capabilities, configurations, and sharing settings. Everything works exactly as before.

Why Agents?

When we launched Assistants in the summer of 2023, the market was figuring out basic functionality, like how to let AI work with a few documents. Since then, the capabilities have grown significantly. What started as rather simple chatbots can now handle large file collections, work with tabular data, connect to your tools, and much more. They use agentic behavior to choose the right approach and tools for each task, working within the configuration you define.

The term "Agent" has become the industry standard for what we used to call Assistants. Many companies, such as Microsoft and Google Enterprise AI, use this terminology. More importantly, we've heard from many of you over the past months that users are used to the term "Agents" or even ask whether Langdock has agents available.

Why now?

This change comes with the launch of Workflows a few weeks ago. Agents and Workflows are complementary products: Agents are your interactive AI assistants for specific tasks, while Workflows let you chain multiple building blocks together (including multiple agents) to automate larger processes in the background.

What does this mean for you?

No action is required from you! The transition happened automatically, and we've updated all documentation to reflect the new terminology.

The assistant API remains unchanged by these changes for now. There will be a separate notification early next year to communicate the changes.

The Langdock platform now consists of the following products: Chat, Agents, Workflows, Integrations, and API. Renaming a core product isn't something we do lightly. We've thought carefully about this and talked to many of you. Ultimately, it made sense for us given how the product and market have evolved.

We'd love to hear your feedback on how we can continue to improve Agents for you! 🙌

  • Support for Gemini 3 Pro: We added support for Gemini 3 Pro. The model required some additional configuration options to function properly. Currently, the model is only available as a global deployment and not yet as an EU-hosted model. BYOK customers can add the model in the model configuration. For customers who use models offered by Langdock, we added the model as a global deployment, and admins can enable it in the workspace settings.
  • Deactivate workflow nodes: Workflow editors can now deactivate workflow nodes by clicking on the three dots at the top right.
  • Building workflow triggers: Until now, you had to be allowed to build custom integrations and have workflow access to build triggers for integrations. Now, all users who are allowed to build integrations can build triggers. You can go to your custom integration and add the trigger like you would add an action.
  • Updated MCP version: We upgraded our MCP support to version 2025-11-25 to support additional MCP servers. Previous MCP servers are still supported.
  • Change order of image models: Admins of BYOK workspaces can now change the order of image models, like the order can be changed for other models.
  • Agent Forms: Forms in agents had up to 15 fields until now. We increased the limit to 25 fields.
  • API to create and update agents: We launched new API endpoints to create new agents and update existing agents via API. See our assistant API documentation here.