FigyTerm v0.0.24

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.24_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.24_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.24_amd64.AppImage
./FigyTerm_0.0.24_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.24_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.24-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.24_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.24_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.23

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.23_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.23_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.23_amd64.AppImage
./FigyTerm_0.0.23_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.23_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.23-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.23_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.23_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.22

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.22_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.22_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.22_amd64.AppImage
./FigyTerm_0.0.22_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.22_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.22-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.22_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.22_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.21

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.21_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.21_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.21_amd64.AppImage
./FigyTerm_0.0.21_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.21_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.21-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.21_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.21_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.20

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.20_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.20_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.20_amd64.AppImage
./FigyTerm_0.0.20_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.20_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.20-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.20_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.20_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.19

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.19_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.19_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.19_amd64.AppImage
./FigyTerm_0.0.19_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.19_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.19-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.19_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.19_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.18

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.18_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.18_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.18_amd64.AppImage
./FigyTerm_0.0.18_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.18_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.18-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.18_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.18_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.17

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.17_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.17_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.17_amd64.AppImage
./FigyTerm_0.0.17_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.17_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.17-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.17_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.17_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.16

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.16_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.16_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.16_amd64.AppImage
./FigyTerm_0.0.16_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.16_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.16-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Installation (Windows)

Download FigyTerm_0.0.16_x64-setup.exe and run it. It installs for
the current user, needs no administrator rights, and updates itself from
then on.

Windows will show "Windows protected your PC" the first time, because
the installer isn't code-signed. Click More info, then Run anyway.
There's no way around this yet: unlike macOS there's no flag to clear,
and reputation accrues per binary as downloads accumulate.

FigyTerm_0.0.16_x64_en-US.msi is also published for deployment via
Group Policy or Intune. It does not self-update — a managed install
stays managed by whatever pushed it.

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.

FigyTerm v0.0.14

Updating

FigyTerm updates itself from here on — it checks for new versions and
installs them in-app, with no Gatekeeper prompt and no xattr step.
If you're coming from v0.0.6 or earlier, this one install is manual;
after it, updates are automatic.

Installation (macOS)

Two ways to install. Both give you the same app.

Option 1 — install script (recommended)

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

One line, no security dialog, no xattr step. It picks the right build for
your Mac and installs to /Applications.

Why it's simpler: FigyTerm isn't code-signed with an Apple Developer ID, and
macOS quarantines anything downloaded by a browser. curl isn't a
browser, so this route avoids the problem rather than working around it.
Read the script
before running it.

Option 2 — download the .dmg manually

1. Download FigyTerm_0.0.14_aarch64.dmg (Apple Silicon) or
   FigyTerm_0.0.14_x64.dmg (Intel)

2. Open the .dmg and drag FigyTerm into Applications

3. Clear the quarantine flag macOS added during the download:

   xattr -cr /Applications/FigyTerm.app
   

4. Launch FigyTerm

Step 3 isn't optional — without it macOS reports "FigyTerm is damaged and
can't be opened", which only means the app is unsigned.

Installation (Linux)

Three formats, with one difference worth knowing.

AppImage (recommended) — runs on any distro, and updates itself:

chmod +x FigyTerm_0.0.14_amd64.AppImage
./FigyTerm_0.0.14_amd64.AppImage

Debian / Ubuntu: sudo apt install ./FigyTerm_0.0.14_amd64.deb
Fedora / RHEL: sudo dnf install ./FigyTerm-0.0.14-1.x86_64.rpm

A .deb or .rpm install belongs to your package manager, so FigyTerm
won't replace its own files — it tells you a new version exists and leaves
the install to you. The AppImage is the one that updates in place.

If the window comes up blank — some Nvidia and older Mesa drivers do this
to WebKitGTK — start it with:

WEBKIT_DISABLE_DMABUF_RENDERER=1 figyterm

Full details: Installation guide

Troubleshooting

"FigyTerm can't be opened because it is from an unidentified developer"
Open System Settings > Privacy & Security, scroll down, and click
Open Anyway. On macOS 15 and later this is the only route — Apple removed
the old right-click > Open shortcut.

"FigyTerm is damaged and can't be opened"
The quarantine flag is still set. Run:

xattr -cr /Applications/FigyTerm.app

Keychain access popup
macOS may ask to access your keychain. Click Allow or Always Allow. This is normal for apps that interact with system credentials.

What's New

See CHANGELOG for details.