Retool CLI Public Beta

📣 Retool Announcements 💥 Product Updates
1

Live on Cloud • Team • Business • Enterprise | Public Beta
4.62 Edge • Team • Business • Enterprise | Public Beta
4.34.4 Stable • Team • Business • Enterprise | Public Beta

The Retool CLI is now available in public beta. It enables you to build, manage, and publish Retool-native React apps from the command line and with the help of your chosen code development agent harness, like Claude Code or Codex.

With this tool, you can write and validate app code directly on your machine. You can use the CLI independently or pair it with a local development agent. Follow the installation instructions to get started, learn how the CLI works, or compare the CLI to the MCP.

Note
Retool supports an existing CLI that is used exclusively for classic apps. This CLI is now deprecated. It will be removed from cloud instances on March 1, 2027, and from stable instances in the Q2 2027 stable release.

6 Likes
Retool CLI push blocked by cliFileAuthorization on unchanged /context/ files created by Retool Agent
Retool CLI 0.4.65 returns 401 on /cli/resource-types/metadata after successful OAuth login
2

Hi Darren,

We are currently building a production ERP on Retool Business, using Supabase/PostgreSQL as the backend and Retool Apps Builder as the frontend.

We would like to continue with Retool, but we have experienced recurring Apps Builder development issues, including Preview/runtime instability, sandbox provisioning failures and excessive browser memory usage. We already have an active support case with detailed technical evidence (#56005).

We are now evaluating the new Retool CLI/Git workflow as our primary development environment instead of relying on the browser-based Apps Builder editor.

Our key question is whether the CLI is mature enough to become the main development workflow for a production business-critical ERP, while still using Retool for preview, publishing, auth, hosting and runtime.

We would particularly appreciate guidance from someone on the CLI / Apps Builder engineering team regarding:

  • migrating an existing Apps Builder application safely to a CLI/Git workflow;

  • preserving existing unpublished Editor work;

  • which Apps Builder development issues the CLI actually bypasses;

  • recommended Git/branch/release workflow for a production application;

  • current limitations or risks of using the CLI Public Beta for a business-critical application.

We are not looking to replace Retool if this workflow can provide a stable development path. We are trying to make the right long-term architecture decision before investing further development effort.

If someone from the CLI / Apps Builder engineering team could provide guidance — or even a short technical call — it would be extremely helpful.

Thank you,
Péter

1 Like
3

Hi Retool Team,

I wanted to drop a quick comment here regarding the Retool CLI. :slight_smile:

I’ve only used it for a week or so now, but I have to say I absolutely love it. The workflow using Claude Code to build/test/deploy the app is just incredible. The ability to just sit down with a stakeholder and iterate ideas in real time on real data is fantastic.

Great job with this one so far!

4 Likes
4

Echoing this, CLI is absolutely incredible, it opens a world of possibilities, and it has been an excellent execution from the Retool team.

3 Likes