Internationalization (i18n) is now generally available for organizations on the Enterprise plan. This allows you to localize Retool app content and data.

Retool now supports managing permissions using role-based access control in public beta. You can create roles with granular permissions so groups can manage certain organization settings without full administrator access.

Role-based permissions offer much greater access control than Retool's existing group permissions functionality. For example, a Design team may need access to your organization's branding settings to ensure the Retool organization follows branding styles and guidelines. Rather than give the team members admin access, role-based permissions allow for granular control over what specific settings they can access.

Once you configure the necessary roles to control access, you can apply them to any number of groups. Retool will eventually transition away from per-group permissions to role-based access controls as the method with which you manage permissions.

To enable this feature, navigate to Settings > Beta and enable Permissions v2.

OAuth 2.0 is now supported when adding an MCP server as a tool for an agent.

Retool Agents is available on Retool's stable release 3.253.0.

To enable Retool Agents in Self-hosted Retool 3.253.0 and later, toggle the AI Agents feature flag in Settings > Beta.

Retool now provides a built-in integration for Databricks Lakebase, a fully managed Databricks Postgres database built on lakehouse architecture.

Self-hosted organizations using Source Control to protect apps can opt into the public beta of multi-instance releases. This feature enables you to publish different release versions of apps across multiple deployment instances. This is particularly useful if you want to test a newer version of an app on a test instance first.

Retool removed the preview release of Agents for self-hosted organizations since Agents is now in public beta with the 3.234.0 edge release and it will be available in 3.253 stable. This preview release was intended for deployment into a non-production environment, and was created as a mechanism to allow Self-hosted organizations the opportunity to create agents prior to their availability in an edge or stable release.

Retool Agents is now in public beta on Self-hosted Retool 3.234.0.

To enable Retool Agents in Self-hosted Retool 3.234.0 and later, the AGENTS_ENABLED environment variable must be set to true.

A preview release of Retool Agents is currently available to self-hosted organizations for deployment into a non-production environment. This preview release is intended to allow customers to preview and create proof-of-concepts that show how agents may work in their environment.

As Retool is continuously working to develop and improve Retool Agents to meet the high standards required for production environments, this preview release is not intended for production use and this build should not be deployed in an existing Retool installation or deployment. Retool recommends that self-hosted organizations create a new deployment in a private network alongside resources to which you intend to connect. Retool reserves the right to make changes to the agents preview without notification.

Retool Agents makes it simple for builders to automate work using large-language models (LLMs) by creating agents. Agents are systems that can complete or delegate tasks based on LLM reasoning.

Agents call tools—for example, workflows, functions, or other agents—to gather information and complete or delegate actions. When invoked, an agent:

1. Receives a task, or input, as natural language. Tasks are provided as input to agents via written instructions.
2. Uses an LLM to decide whether to respond to the input, get more information, or take action in another system.
3. Provides the result of the tool call back to the LLM, and the LLM reasons in an open-ended cycle called an agentic loop without a pre-defined stopping point.
4. Finally, the agent responds to your original message or question once it reaches a conclusion.

You can invoke an agent using any of the following trigger methods:

• The built-in chat experience in Retool Agents.
• Sending an email to the agent.
• The Agent Chat component in apps.
• The Invoke Agent block in workflows.

You can then test, deploy, evaluate, and monitor your agent directly from Retool.