Downloads of v


Last Update:

04 Apr 2020

Package Maintainer(s):

Software Author(s):

  • Joe Wilm


foss development cli shell bash powershell cmd posix unix linux gnu cygwin msys msys2 mingw graphical console emulator hardware gpu terminal admin

Alacritty (Install)

This is not the latest version of Alacritty (Install) available.

  • 1
  • 2
  • 3 | Updated: 04 Apr 2020



Downloads of v



Software Author(s):

  • Joe Wilm

  • 1
  • 2
  • 3
Alacritty (Install)

This is not the latest version of Alacritty (Install) available.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Dependencies are known to require a reboot on the verifier machine.


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Alacritty (Install), run the following command from the command line or from PowerShell:


To upgrade Alacritty (Install), run the following command from the command line or from PowerShell:


To uninstall Alacritty (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade alacritty.install -y --source="'INTERNAL REPO URL'" --version="''" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade alacritty.install -y --source="'INTERNAL REPO URL'" --version="''" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install alacritty.install
    name: alacritty.install
    version: ''
    state: present

See docs at

chocolatey_package 'alacritty.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller alacritty.install
    Name     = "alacritty.install"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'alacritty.install':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 04 Apr 2020.



Travis build Status
Appveyor build Status


Alacritty is a terminal emulator with a strong focus on simplicity and
performance. With such a strong focus on performance, included features are
carefully considered and you can always expect Alacritty to be blazingly fast.
By making sane choices for defaults, Alacritty requires no additional setup.
However, it does allow configuration of many aspects of the

The software is considered to be at a beta level of readiness -- there are
a few missing features and bugs to be fixed, but it is already used by many as
a daily driver.

Further information

On Windows, Alacritty also requires Microsoft's VC++ redistributable.

For Windows versions older than Windows 10 (October 2018 Update), Alacritty
requires winpty to emulate UNIX's PTY API. The agent is a single binary
(winpty-agent.exe) which must be in the same directory as the Alacritty


You can find the default configuration file with documentation for all available
fields on the GitHub releases page for each release.

Alacritty looks for the configuration file at the following paths:

  1. $XDG_CONFIG_HOME/alacritty/alacritty.yml
  2. $XDG_CONFIG_HOME/alacritty.yml
  3. $HOME/.config/alacritty/alacritty.yml
  4. $HOME/.alacritty.yml


On Windows the config file is located at:



A full guideline about contributing to Alacritty can be found in the file.

Issues (known, unknown, feature requests, etc.)

If you run into a problem with Alacritty, please file an issue. If you've got a
feature request, feel free to ask about it. Please just keep in mind Alacritty
is focused on simplicity and performance, and not all features are in line with
that goal.

Before opening a new issue, please check if it has already been reported.
There's a chance someone else has already reported it, and you can subscribe to
that issue to keep up on the latest developments.


Is it really the fastest terminal emulator?

In the terminals we've benchmarked,
Alacritty is either faster or way faster than the others. If you've found a
case where this isn't true, please report a bug.

Why isn't feature X implemented?

Alacritty has many great features, but not every feature from every other
terminal. This could be for a number of reasons, but sometimes it's just not a
good fit for Alacritty. This means you won't find things like tabs or splits
(which are best left to a window manager or terminal multiplexer) nor
niceties like a GUI config editor.


Alacritty discussion can be found in #alacritty on freenode.


Alacritty is released under the Apache License, Version 2.0.

$packageName = "alacritty.install"
$url64 = ""
$checksum64 = "a24e62fb328416e3523b511d825e277827f39bbe764ba786436d9b8874caf885baf83e72f53c33d33ff69afe8b32498dea23bb491c63d08854f67a7dfe01794c"
$oldInstallDir = Join-Path $(Get-ToolsLocation) "alacritty"

$preexisting = Test-Path -Path $oldInstallDir -PathType Container
if ($preexisting) {
	Write-Host -ForegroundColor yellow "WARNING: Alacritty Portable detected."
	Write-Host -ForegroundColor yellow "If you installed a previous version of this package the semantics have changed."
	Write-Host -ForegroundColor yellow "This is now a install package, and will install the MSI version of this software instead."
	Write-Host -ForegroundColor yellow "If you are OK with this, or installed portable through your own means, ignore this message."
	Write-Host -ForegroundColor yellow "Otherwise you should delete the files at $oldInstallDir to prevent conflicts in the future."

$ErrorActionPreference = 'Stop'
$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
$packageArgs = @{
    PackageName    = $packageName
    FileType       = "msi"
    SoftwareName   = "Alacritty"
    Url64bit       = $url64
	Checksum64     = $checksum64
	ChecksumType64 = "sha512"
    SilentArgs     = "/qn /norestart"
    ValidExitCodes = @(0, 3010, 1641)
Install-ChocolateyPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Alacritty (Install) 0.10.0 1106 Wednesday, January 26, 2022 Approved
Alacritty (Install) 0.9.0 3513 Sunday, August 8, 2021 Approved
Alacritty (Install) 0.8.0 2234 Wednesday, May 19, 2021 Approved
Alacritty (Install) 0.7.2 2258 Thursday, March 4, 2021 Approved
Alacritty (Install) 0.7.1 1758 Tuesday, January 12, 2021 Approved
Alacritty (Install) 0.7.0 284 Monday, January 11, 2021 Approved
Alacritty (Install) 1579 Wednesday, November 25, 2020 Approved
Alacritty (Install) 0.5.0 2817 Monday, August 3, 2020 Approved


  • Minimum Rust version has been bumped to 1.37.0

  • Added Rust features x11 and wayland to pick backends, with both enabled by default

  • Capitalized the Alacritty.desktop file


  • Live config reload for window.title


  • Pressing additional modifiers for mouse bindings will no longer trigger them

  • Renamed WINIT_HIDPI_FACTOR environment variable to WINIT_X11_SCALE_FACTOR

  • Print an error instead of crashing, when startup working directory is invalid

  • Line selection will now expand across wrapped lines

  • The default value for draw_bold_text_with_bright_colors is now false

  • Mirror OSC query terminators instead of always using BEL

  • Increased Beam, Underline, and Hollow Block cursors' line widths

  • Dynamic title is not disabled anymore when window.title is set in config


  • Config option auto_scroll, which is now always disabled

  • Config option tabspaces, which is now fixed at 8


  • Incorrect default config path in --help on Windows and macOS

  • Semantic selection stopping at full-width glyphs

  • Full-width glyphs cut off in last column

  • Crash when starting on some X11 systems

  • Font size resetting when Alacritty is moved between screens

  • Limited payload length in clipboard escape (used for Tmux copy/paste)

  • Alacritty not ignoring keyboard events for changing WM focus on X11

  • Regression which added a UNC path prefix to the working directory on Windows

  • CLI parameters discarded when config is reload

  • Blurred icons in KDE task switcher (alacritty.ico is now high-res)

  • Consecutive builds failing on macOS due to preexisting /Application symlink

  • Block selection starting from first column after beginning leaves the scrollback

  • Incorrect selection status of the first cell when selection is off screen

  • Backwards bracket selection

  • Stack overflow when printing shader creation error

  • Underline position for bitmap fonts

  • Selection rotating outside of scrolling region

  • Throughput performance problems caused by excessive font metric queries

  • Unicode throughput performance on Linux/BSD

  • Resize of bitmap fonts

  • Crash when using bitmap font with embeddedbitmap set to false

  • Inconsistent fontconfig fallback

  • Handling of OpenType variable fonts

  • Expansion of block-selection on partially selected full-width glyphs

  • Minimize action only works with decorations on macOS

  • Window permanently vanishing after hiding on macOS

  • Handling of URLs with single quotes

  • Parser reset between DCS escapes

  • Parser stopping at unknown DEC private modes/SGR character attributes

  • Block selection appending duplicate newlines when last column is selected

  • Bitmap fonts being a bit smaller than they should be in some cases

  • Config reload creating alternate screen history instead of updating scrollback

  • Crash on Wayland compositors supporting wl_seat version 7+

  • Message bar not hiding after fixing wrong color value in config

  • Tabstops cleared on resize

  • Tabstops not breaking across lines

  • Crash when parsing DCS escape with more than 16 parameters

  • Ignoring of slow touchpad scrolling

  • Selection invisible when starting above viewport and ending below it

  • Clipboard not working after TTY switch on Wayland

  • Crash when pasting non UTF-8 string advertised as UTF-8 string on Wayland

  • Incorrect modifiers tracking on X11 and macOS, leading to 'sticky' modifiers

  • Crash when starting on Windows with missing dark mode support

  • Variables XCURSOR_THEME and XCURSOR_SIZE ignored on Wayland

  • Low resolution mouse cursor and decorations on HiDPI Wayland outputs

  • Decorations visible when in fullscreen on Wayland

  • Window size not persisted correctly after fullscreening on macOS

  • Crash on startup with some locales on X11

  • Shrinking terminal height in alt screen deleting primary screen content

Discussion for the Alacritty (Install) Package

Ground Rules:

  • This discussion is only about Alacritty (Install) and the Alacritty (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Alacritty (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus