Skip to content
Command specs

Completions that know your tools

A spec describes a command's subcommands, options and arguments. FigyTerm reads the format Fig used, so the ecosystem of community completions works unchanged — and adding your own CLI is a single TypeScript file.

Spec authoring guideHow autocomplete works

Built in

Eight commands covered out of the box

These ship with the app. Anything without a spec still gets filesystem paths, directories and shell built-ins, so autocomplete is never simply absent.

Specs are evaluated locally. Nothing about the command you are typing is ever sent over the network.

Missing your tool? A spec is one file and a pull request — the authoring guide walks through it end to end.

  • gitSubcommands, branches, options
  • dockerCommands, containers, images, options
  • docker composeServices, commands, options
  • npmScripts, packages, options
  • pnpmScripts, workspaces, options
  • yarnScripts, packages, options
  • uvScripts from pyproject.toml, options
  • cdDirectories, recent-first ordering
  • Plus filesystem paths, shell built-ins and your own specs.

Why the format matters

Fig's spec catalogue did not have to die with Fig

Fig's autocomplete was discontinued after the AWS acquisition, but the specs the community wrote for it are just TypeScript describing commands — a genuinely useful artefact, independent of the app that read them. FigyTerm reads the same shape, so that work carries over instead of being rewritten.

Give your terminal its whole workbench

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