What terminals does Fig support?

  • macOS Terminal
  • iTerm
  • Hyper
  • VSCode embedded terminal

What shells does Fig support?

  • zsh
  • fish
  • bash

Where can I get updates on future integrations?

Is Fig hiring?

What is Fig's privacy policy?

You can read our privacy policy here:

How can I contact you?

Visit our contact page

How do I report a bug?

Where can I make a feature request?

What network requests does Fig make?

Fig is designed to be very modular. This modularity makes it easy to push hotfixes to users immediately without requiring a full update to the desktop app.

  • Installing Fig: downloads our installation scripts from withfig/config
  • Downloading up to date autocomplete specs with fig update: withfig/autocomplete
  • Loading apps like autocomplete: we host all Fig apps ourselves. They are loaded once and only reload when prompted or after restarting Fig
  • Usage metrics:
  • Our update server - check to see if new version exists and is ready for download
  • Completion spec network requests:
    • Sometimes, completion specs need to make network requests in order to offer correct completions
      • for example To offer package suggestion in npm install, we need to search over the npm package registry
    • Icons: Completion specs can also have custom icons that are loaded at runtime and hit the relevant img URL
      • for example the Heroku completion spec uses the Heroku icon. This image is hosted on the heroku site
    • We try to avoid completion spec network requests entirely. We download almost all icons locally ourselves. And before merging a spec, we do a thorough review of all network requests to determine if they are necessary. We will not merge them if they are not