Question 1

What is FigyTerm?

Accepted Answer

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.

Question 2

Is FigyTerm the same as Fig or figterm?

Accepted Answer

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.

Question 3

What happened to Fig, and what replaced it?

Accepted Answer

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.

Question 4

Is FigyTerm a good Fig alternative?

Accepted Answer

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.

Question 5

Does FigyTerm send my commands anywhere?

Accepted Answer

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.

Question 6

Which platforms are supported?

Accepted Answer

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.

Question 7

Do all the features work on every platform?

Accepted Answer

Almost. Autocomplete, panes, tabs, history search, the system monitor, the command palette, the embedded browser, the code editor, the API client, the Claude Code window and the drawing board work everywhere. The one exception is the Oh My Zsh theme picker, which reads ~/.zshrc and so only applies where zsh does — macOS and Linux. On Windows the equivalent would be Oh My Posh, which FigyTerm doesn't manage yet.

Question 8

Does all of this make it slow to start?

Accepted Answer

No, because none of it loads at launch. The editor, browser, API client, Claude window and drawing board are each loaded the first time you open them, so a session that only uses the terminal pays for the terminal. The base app is a Tauri 2 binary of around ten megabytes with a Rust PTY behind it.

Question 9

Which Linux package should I pick?

Accepted Answer

The AppImage, unless you specifically want your package manager in charge. It runs on any distro, needs no root, and it's the only Linux format FigyTerm's updater can replace in place. A .deb or .rpm install belongs to apt or dnf, so FigyTerm will tell you when a new version exists but leave installing it to you.

Question 10

Why does Windows say “Windows protected your PC”?

Accepted Answer

Because the installer isn't code-signed. Click More info, then Run anyway. Unlike macOS there's no flag to clear and no curl workaround — SmartScreen builds reputation per binary as downloads accumulate, and only an expensive EV certificate grants it up front.

Question 11

Why does macOS say the app is damaged?

Accepted Answer

FigyTerm is not code-signed with a paid Apple Developer ID, so macOS quarantines it when a browser downloads it. Run xattr -cr /Applications/FigyTerm.app once and it opens normally. The install script avoids this entirely, because curl never sets the quarantine flag.

Question 12

Do I need Oh My Zsh or a special shell?

Accepted Answer

No. On macOS and Linux FigyTerm launches whatever your $SHELL points to — zsh, bash and fish all work out of the box. On Windows it prefers PowerShell 7, then Windows PowerShell, then cmd.exe. Oh My Zsh is optional and only unlocks the live theme picker in Settings.

Question 13

How do updates work?

Accepted Answer

FigyTerm updates itself. The built-in Tauri updater checks GitHub Releases and installs new versions in one click, so you only ever install manually once. The exceptions are the packages meant to be managed by something else — a Linux .deb or .rpm and the Windows .msi — where FigyTerm reports the new version and leaves the install to whatever put it there.

Question 14

What does it cost?

Accepted Answer

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

Question 15

Does autocomplete work with my shell?

Accepted Answer

Yes. Completions are computed by FigyTerm itself rather than by the shell, so zsh, bash, fish, PowerShell 7 and cmd.exe all behave the same. Nothing is installed into your dotfiles and no shell plugin is required.

Question 16

Can I add autocomplete for my own CLI?

Accepted Answer

Yes. Specs are plain TypeScript definitions in the repository, and the spec authoring guide walks through adding a new command. Pull requests for new specs are welcome.

Question 17

Is it slower than my shell's own completion?

Accepted Answer

No. Matching runs in Rust against specs already in memory, with no subprocess to spawn and no network round-trip, so the popup keeps up with typing.

Question 18

How many panes can one tab hold?

Accepted Answer

Four, split horizontally, vertically or both. Each one is an independent PTY with its own working directory, its own scrollback and its own autocomplete.

Question 19

Does the system monitor cost performance?

Accepted Answer

It samples only while the modal is open, and the charts are drawn from a small rolling window. Closing it stops the sampling entirely.

Question 20

Does the Oh My Zsh theme picker work on Windows?

Accepted Answer

No. It reads ~/.zshrc and so only applies where zsh does — macOS and Linux. The Windows equivalent would be Oh My Posh, which FigyTerm does not manage yet.

Question 21

Is the built-in editor meant to replace my IDE?

Accepted Answer

No, and it does not pretend to. It is for the edits you would otherwise break flow for — patch a config, fix the line a stack trace just pointed at, read a README. There is no debugger and no test runner. Your editor keeps your project; this one keeps you in the terminal.

Question 22

Does it have IntelliSense?

Accepted Answer

Optionally. Word completion from the open document works with no setup, and language server support adds real diagnostics, hover, completion, go-to-definition and rename using servers you already have installed.

Question 23

Does opening the editor slow the terminal down?

Accepted Answer

No. The editor is loaded the first time you open it, not at launch, so a session that never opens it never pays for it.

Question 24

Does it use my git configuration?

Accepted Answer

Yes. FigyTerm runs the git on your PATH rather than reimplementing it, so your hooks, aliases, signing configuration and credential helper all apply.

Question 25

Can I stage individual hunks?

Accepted Answer

Not yet — staging is file-level. Hunk-level staging, branch switching and pull are deliberately left to the command line for now.

Question 26

What happens to a discarded change?

Accepted Answer

The file goes to the system trash, not to nowhere. A discard you regret is recoverable.

Question 27

Which language servers are supported?

Accepted Answer

The ones you install. FigyTerm speaks the Language Server Protocol and launches the server you point it at, so anything protocol-compliant works. Nothing is bundled and nothing is downloaded on your behalf.

Question 28

Will this slow the terminal down?

Accepted Answer

Only while a server is running, and only in the editor. Language server support is off until you turn it on, and the server starts when a matching file is opened rather than at launch.

Question 29

Is there IntelliSense without a language server?

Accepted Answer

There is word completion drawn from the open document, plus highlighting, folding and bracket awareness from the syntax tree the editor already parses. Type-aware completion needs a server.

Question 30

Do I need Claude Code installed?

Accepted Answer

Yes. FigyTerm hosts the CLI, it does not ship it. Install `claude` the way you normally would and FigyTerm will run it.

Question 31

What happens to a conversation when I switch projects?

Accepted Answer

Nothing. It keeps running. That is the point of the feature — the switcher moves what you are looking at, not what is executing.

Question 32

Is the CLI modified in any way?

Accepted Answer

No. What is inside the window is Claude Code exactly as it ships. FigyTerm draws the frame, the project model and the switcher around it.

Question 33

Can I import my existing collections?

Accepted Answer

Yes. Collection Format v2.1.0 imports and exports, v2.0.0 imports. Import is lossless — the original document is kept alongside the normalised model, so an export round-trips back to what you brought in.

Question 34

Does my API data go to a server?

Accepted Answer

Only to the API you are calling. Collections, history and variables live in SQLite on your machine. Postgres sync is opt-in and points at a server you choose.

Question 35

Is this meant to replace a full API platform?

Accepted Answer

No. v1 is REST over HTTP and HTTPS, aimed at the request you want to fire without leaving the terminal. There is no mock server, no monitor and no team workspace.

Question 36

Is this real Excalidraw?

Accepted Answer

Yes — the Excalidraw canvas itself, embedded. The toolbar, the shapes and the feel are the ones you already know.

Question 37

Where are my drawings stored?

Accepted Answer

Locally, on your machine. There is no account and no sync — a drawing project exists on the computer you drew it on.

Question 38

Can I export a drawing?

Accepted Answer

Excalidraw's own export is there for getting a diagram into a document or an issue.

Question 39

Is it a full browser?

Accepted Answer

It is a native webview with tabs, an address bar and back, forward and reload. Bookmarks, extensions and profiles are not there — this is for reading documentation beside the command, not for replacing your browser.

Question 40

Will sites that block iframes work?

Accepted Answer

Yes. It is a real child webview, not an iframe, so `X-Frame-Options` and frame-ancestors headers are not an obstacle.

Question 41

Does it share cookies with my main browser?

Accepted Answer

No. It has its own webview storage, separate from Chrome, Safari or Firefox.

General