https://res.cloudinary.com/djkmxf6kr/image/upload/v1672778957/site/team/chay_blyzpx.jpg

https://res.cloudinary.com/djkmxf6kr/image/upload/v1672776229/site/team/parssa_jedrst.jpg

https://res.cloudinary.com/djkmxf6kr/image/upload/v1672775560/site/team/grant_y0y5zr.jpg

https://res.cloudinary.com/djkmxf6kr/image/upload/v1672775558/site/team/brendan_ljqpap.png

https://res.cloudinary.com/djkmxf6kr/image/upload/v1672775562/site/team/matt_xbkvk1.webp

The public scripts store is now available! You can search for public scripts for other individuals and teams and execute them immediately.

To get started download Fig and go to the “Scripts & CLIs” page, then select the “Scripts Store” page to see all publicly available scripts.

To publish a script go to your script and click the “Public” check box on the “Settings” page

Fig 2.12 is now available, to update click the Fig icon in your menu bar and select “Check for updates…” or use your package manager

[New] Improved filepicker in the Scripts TUI with better navigation and easier search

[New] Add support for public scripts in the CLI

[Fix] Improved script caching to prevent hangs with caching too many scripts

[Fix] Make script invocations include exit code again

Build Internal CLI tools using Fig Scripts

Top engineering orgs, like Shopify, Brex, 

, maintain internal CLI tools to boost developer productivity.

Now, with Fig Scripts, your team can have the same 10x developer experience with a fraction of the work. 

Teams use internal CLI tools to codify terminal workflows and improve developer productivity.

It let new engineers focus on getting up to speed with their new projects, not messing around figuring out how various systems fit together.

It helped everyone stay in the flow and focused on their tasks at a higher level.

It reduced the amount of edge-case “stuff” floating in developers’ brains from day-to-day (“ugh, where do the log files live again?”).

Improvements made by one person made everyone’s work easier.

and create a New CLI. Once you create a CLI tool, everyone on your team will have be able to run use it.

Move commands around or add new commands in the Fig Dashboard


Using the Fig Dashboard, you’ll be able to add new commands & modify the structure of the CLI tool. Changes you make are automatically shared with your entire team.

Internal CLI tools are automatically distributed to your team. Changes sync instantly.

You can move existing Fig Scripts into your CLI tool or you can create new commands as needed. 

Build your team’s internal CLI tool with Fig

 way to create internal CLI tools and share scripts across your engineering team. You can build and distribute an internal developer tool in 

 makes it easy to distribute your CLI tool and push changes, without writing your own self-updating logic and backend.

Out-of-the-box error reporting and usage monitoring

 lets you gain insights into blockers, helping your team move faster.

 adds helpful guardrails to the execution process, preventing mistakes and enabling new engineers to get up to speed quickly.

If you have any feedback or want a Fig engineer to help onboarding your team, don’t hesitate to reach out to 

[New] Fig Scripts now run inline in the terminal

[Fix] Fig Scripts now properly work in Bash 3 where bracketed pasting would case issues previously

[Fix] Shell dotfiles comments will be ignored by the dotfile integration installer and status check

[Fix] Terminal could become unresponsive when autocomplete ran too many commands, this no longer happens

Fig login screen showing “Continue with GitHub” button

Click the “Continue with GithHub” button on the sign in screen

Click “Allow” on the GitHub popup window when asked if to allow Fig

Note, if you have an existing Fig account it can be linked to GitHub if your “Primary Email” on GitHub is the same as your Fig account’s email, otherwise you will create a new Fig account.

Fig 2.11 is now available, to update click the Fig icon in your menu bar and select “Check for updates…” or use your package manager

[New] Script input descriptions now show in TUI

[Fix] Scripts will not hang after the execution is finished

[Fix (macOS)] Do not prompt uninstall page when upgrading with 

[Fix (macOS)] Make input method dependent terminals (Kitty, Alacritty, Jetbrains) work on external monitors

 of stuff. But currently the only way to find out about it is in our monthly newsletter or launches on Twitter. These are easy to miss.

Here’s how we plan to structure our content ongoing:

: A monthly summary of the top features we’ve shipped

: In-depth posts about products, engineering, or the company!

Fig 2.10 is now available, to update click the Fig icon in your menu bar and select “Check for updates…” or use your package manager

[New] #FigWrapped is available again, now with random facts about your year in the terminal

[New] Experimental offline support for autocomplete, you can enable with 

fig settings autocomplete.offline-support true

[New] The SSH Integration is automatically prompted to be installed on remote machines

[New] The Fig Dotfiles integration is now less aggressive with whitespace and supports 

 to prevent automated installation in your shell configs

[New] Script CLI is now parsed with clap, allowing for more flexible terminal interfaces for script devs

[Fixed (macOS)] Intellij plugin now correctly installs and does not report issues with compatibility

Fig 2.9 is now available, to update click the Fig icon in your menu bar and select “Check for updates…” or use your package manager

[New] ⌘+[ and ⌘+] can now navigate the Fig Dashboard

[Fixed] more details on how to update iTerm Bash Integration in Fig Doctor (

[Fixed] SSH login now falls back to token based login if it can not connect to the desktop application

[New (Linux)] Intellij/Jetbrains IDEs work

[New] Support for Python, Node, and Deno runtimes in scripts 

 command to easily open the scripts page in dashboard

 to prevent the script from being executed as a command in the shell if executing from the TUI

[New] TUI search is sorted by user invocation then team invocation

 to manually refresh the local script cache

[Fixed] Scripts now ensure all required fields are entered when in TUI mode before executing

[Fixed] ctrl-c is handled better with a message that the script was terminated and ends with exit code 130

Fig 2.8 is now available, to update click the Fig icon in your menu bar and select “Check for updates…” or use your package manager

Fig is switching to a 2 week release cycle which means you should both get new features and a changelog every 2 weeks! Let us know you feedback on the changelog here.

[Changed] Fig shell integrations have been massively improved (10x) in start time 🚀

[Fixed] Shell will have correct name in VSCode again (

[Fixed] Autocomplete window will correctly align with cursor when at the end of screen with the description popout

[Fixed (macOS)] Fig input method supports down to macOS 10.13 again (

[New (Linux)] Autocomplete window sticks to window’s bounds

[New] Add support for an easy login flow in SSH sessions

[Fixed] SSH integrations now work in almost all contexts and do not generate errors with VSCode Remote

[Fixed (macOS)] Use native icons for files/folders when using SSH

Release Notes

All the recent changes to Fig

Public Scripts Store

Fig 2.13

Build Internal CLI tools using Fig Scripts

Fig 2.12

Fig now supports GitHub Login

Fig 2.11

Launching the Fig Changelog!

Fig 2.10

Fig 2.9

Fig 2.8