retool-cli
v1.0.30
Published
CLI for Retool
Readme
Retool Classic CLI
[!CAUTION] The Retool Classic CLI is deprecated. It will be removed from cloud instances on March 1, 2027, and from stable instances in the Q2 2027 stable release.
If you're looking for a CLI tool for AI-powered app building, refer to Retool's new CLI.
A simple command line interface for classic apps, workflows, and other functionality on Retool.
Open an issue in this repository for feature requests. PRs welcome!

Installation & Updating
npm install -g retool-cli
Node.js is a requirement, it can be installed here. See this guide to resolve EACCES permissions errors.
Usage Instructions
retool --help
retool <command> --help
Building from Source
git clone https://github.com/tryretool/retool-cli.gitcd retool-clinpm i && npm run devnpm install -g .Installs theretoolcommand globally on your machine.
Contribution Guide
Extending an existing command
- Locate the command file in
src/commands/. - Add a new flag to the
builderobject and provide a clear description. This description will be displayed to the user in the help command. - Handle the new flag by adding an
else if (argv.newFlag)statement to the handler function.
Adding a new command
- Create a new file in the
src/commandsdirectory, ensure it exports aCommandModule. npm run devto start TS compiler.retool loginto authenticate.retool commandNameto test command.
General guidelines
- Retool CLI adheres to the principles outlined in this CLI guide:
- Keep output succinct.
- In help output:
- Use
<>to indicate required params and[]for optional params. - Provide a usage example if appropriate.
- Use
- Errors should be presented in a human-readable format.
- Hide debug output behind a
process.env.DEBUGcheck.
- Any files in
src/commands/directory will become a top-level commands. - Shared logic should be placed in
src/utils/directory.
Publishing to NPM (for Retool employees)
- Bump version in
package.json,npm install, commit changes npm run buildnpm publish
