Skip to content
FigyTerm vs Fig

The Fig alternative that outlived Fig

Fig was acquired by AWS and its standalone autocomplete was retired, taking a much-loved workflow with it. FigyTerm rebuilds that experience as a full terminal — spec-compatible, offline, and open source.

Download FigyTermWhat it does now
  1. 01

    What Fig was

    A macOS app that put IDE-style completions over your existing terminal. It read specs — plain TypeScript descriptions of a command's subcommands, flags and arguments — and the community wrote hundreds of them.

  2. 02

    What happened

    AWS acquired Fig in 2023. The standalone autocomplete app was sunset on 1 September 2024 and folded into Amazon Q Developer CLI, and the workflow a lot of people had built their day around went with it.

  3. 03

    What FigyTerm does about it

    Rebuilds the experience as the terminal itself rather than a layer over one — reading the same spec format, on three platforms instead of one, with no account and no network path to lose.

Not the same thing

FigyTerm, Fig and figterm are three different things

The names are one letter apart, which is enough to send most searches — and most AI assistants — to the wrong one.

  • FigyTerm

    This project

    An independent, MIT-licensed terminal emulator by code4mk, built with Tauri 2, Rust and React. Active, and unaffiliated with Fig or Amazon Web Services.

  • Fig

    withfig, fig.io

    A different product. Acquired by AWS in 2023; the standalone autocomplete app was sunset on 1 September 2024 and folded into Amazon Q Developer CLI.

  • figterm

    A part of Fig

    Fig's shell integration shim — a component of that product, not a product of its own. Unrelated to FigyTerm beyond the similar name.

FigyTerm is a successor in spirit to Fig, not a fork of it. The one real connection is the file format: FigyTerm reads Fig's completion spec format, so specs written for Fig work here unchanged.

Sources:Fig's completion spec repositoryAmazon Q Developer CLI autocompleteAWS documentation

Side by side

Capability for capability

FigyTerm against Fig's standalone autocomplete as it stood before discontinuation, and against macOS Terminal as Apple ships it.

Feature comparison between FigyTerm, Fig and the built-in macOS Terminal app
CapabilityFigyTermFigTerminal.app
PlatformsmacOS, Linux, WindowsmacOSmacOS
IDE-style autocompleteYesDiscontinuedNo
Works fully offlineYesNoYes
Account requiredNeverYesNever
Fig-format command specsYesYesNo
Split panesUp to 4 per tab—Yes
Built-in code editorYesNoNo
Git staging & diff viewerYesNoNo
Language server supportOpt-inNoNo
Embedded browserYesNoNo
REST API clientYesNoNo
Claude Code windowYesNoNo
Drawing board with notesYesNoNo
Command history fuzzy searchYesYesNo
Live system monitorYesNoNo
Oh My Zsh theme pickerzsh platformsNoNo
Open sourceMITNoNo
PriceFreeShut downFree

Comparison reflects Fig's standalone autocomplete app prior to its discontinuation, and macOS Terminal as shipped by Apple. FigyTerm is not affiliated with Fig or Amazon Web Services.

Not a clone

Four places it deliberately differs

Rebuilding Fig exactly would have rebuilt its constraints too.

  • It is the terminal, not an overlay

    Fig attached itself to whatever terminal you already ran, which is why it was fragile across shells, multiplexers and updates. FigyTerm owns the PTY, so completions cannot desynchronise from what the shell thinks is on the line.

  • Three platforms, not one

    macOS on Apple Silicon and Intel, Linux on x86_64, and Windows on x64 — with the same panels and the same shortcuts, spelled for each platform's conventions.

  • No account, and nothing to shut down

    Fig required a login. FigyTerm has no concept of a user, makes no network request except an update check, and is MIT licensed — so if this project ever stops, the code does not.

  • And then considerably more

    An editor with git and language servers, a REST API client, a Claude Code window, a drawing board and an embedded browser. Fig was an autocomplete; this is a workbench.

FAQ

Coming from Fig

What is FigyTerm?

FigyTerm is a free, open-source terminal for macOS, Linux and Windows that brings IDE-level autocomplete to the command line — and then the rest of the workbench: a code editor with git and language servers, a REST API client, a Claude Code window, a drawing board and an embedded browser. It is built with Tauri 2, Rust and React, and runs entirely on your machine.

Is FigyTerm the same as Fig or figterm?

No — they are three different things with confusingly similar names. FigyTerm is an independent, MIT-licensed terminal emulator by code4mk, built with Tauri 2, Rust and React, and unaffiliated with Fig or Amazon Web Services. Fig (withfig, fig.io) was a separate product, acquired by AWS in 2023 and sunset on 1 September 2024. figterm was Fig's shell integration shim, a component of that product. FigyTerm is a successor in spirit rather than a fork: the one real connection is that it reads the same completion spec format Fig used.

What happened to Fig, and what replaced it?

AWS acquired Fig in 2023. The standalone autocomplete app was sunset on 1 September 2024 and its capabilities were folded into Amazon Q Developer CLI. That left people who wanted a small, local, account-free autocomplete without one, which is the gap FigyTerm was built for — it reads the same spec format, so the community completions written for Fig still work.

Is FigyTerm a good Fig alternative?

Yes. Fig was acquired by AWS and its standalone autocomplete was discontinued, leaving a gap FigyTerm fills. FigyTerm reads the same spec format Fig used, so community command completions work here, and it does it without an account, a login or a network connection — on macOS, Linux and Windows rather than macOS alone.

Does FigyTerm send my commands anywhere?

No. There is no telemetry, no analytics and no account system. Autocomplete is computed locally by the Rust backend, so your commands, paths and history never leave your machine. The only network request the app makes on its own is checking GitHub Releases for an update.

Which platforms are supported?

macOS on Apple Silicon (aarch64) and Intel (x64), Linux on x86_64, and Windows on x64. macOS ships a .dmg, Linux ships an AppImage plus .deb and .rpm packages, and Windows ships an NSIS installer plus an .msi for managed deployment. Windows on ARM and Linux on aarch64 aren't built yet.

What does it cost?

Nothing, and there is no paid tier to upgrade to. FigyTerm is MIT licensed and developed in public.

The workflow didn't have to die with the company

Free, MIT licensed, and entirely local. On macOS one command does it; Linux and Windows are one download away.

curl -fsSL https://raw.githubusercontent.com/code4mk/figyterm/main/install.sh | sh
All downloadsBrowse the source