Cocktail
Download
Latest build 1.4.2 · released 18 Sep 2026

Download Cocktail

Linux, x86_64. About 40 MB, signed and reproducible, with nothing else to install. There is no Windows or macOS build.

AppImage

Any distro · x86_64 · 42.1 MB

Download AppImage

Cocktail-1.4.2-x86_64.AppImage

.deb

Debian & Ubuntu · amd64 · 38.9 MB

Download .deb

cocktail_1.4.2_amd64.deb

.rpm

Fedora & RHEL · x86_64 · 39.2 MB

Download .rpm

cocktail-1.4.2.x86_64.rpm

package repositories
# Arch (AUR)
yay -S cocktail-bin

# Debian / Ubuntu
sudo apt install ./cocktail_1.4.2_amd64.deb

# Fedora
sudo dnf install ./cocktail-1.4.2.x86_64.rpm
verify your download
# checksum
sha256sum -c cocktail-1.4.2.sha256

# signature
gpg --verify cocktail-1.4.2.sig

9f3c1b7ae4d02c8815be6f2a71d4903ec55a8b1f7d6e4c20ab93f5178c0d24e6

Before you install

System requirements

Modest. The engine is built to leave headroom for whatever you are testing, not to compete with it.

  • Linux kernel 5.15 or newer, x86_64
  • glibc 2.35+ — Ubuntu 22.04, Debian 12, Fedora 37 or newer
  • 4 GB RAM for the workspace; 8 GB beyond eight instances
  • 400 MB free disk, plus room for session logs
  • X11 or Wayland for the desktop workspace — the CLI runner needs neither

Attaching needs ptrace. Most distributions ship yama/ptrace_scope=1, which restricts attaching to direct children. Cocktail launches instances itself, so the default works — attaching to an already-running client needs the scope relaxed for that session.

echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope

Nothing runs as root. The package installer needs sudo once. After that the workspace, the engine and every instance run entirely as your own user.

cocktail — getting started

Getting started

Set up Cocktail and connect your first instance.

2 of 3

Game installation

/opt/gameclientBrowse

Cocktail files

  • corev1.4.2
  • runtimev1.4.2
  • cocktail.binv1.4.2

Instance connection

Launch the game to establish a connection.

Launch
Waiting for instance…

Changelog

Every build, dated

Builds older than the current release stay downloadable for twelve months.

  1. 1.4.2current18 Sep 2026
    • Retargeted the engine at the 18 Sep client build — attach path rewritten, cold attach down from 5.8s to 4.1s.
    • Decompiler recovers continue statements inside nested numeric loops instead of emitting a flag variable.
    • Instance manager: group broadcast no longer blocks the UI thread while rows report back.
    • Fixed a leak where replay files kept a file descriptor open after the session closed.
  2. 1.4.06 Sep 2026
    • Flame profiler keeps 600 frames instead of 240, and exports a JSON trace.
    • Sandbox capability grants are written to the session log with the line that requested them.
    • Workspace-wide symbol search; fuzzy jump now respects .ctignore.
  3. 1.3.722 Aug 2026
    • Native Wayland session support — the workspace no longer falls back to XWayland.
    • Credential vault moved to per-workspace keys; existing vaults migrate on first open.
    • Idle CPU of an attached-but-paused session drops from 1.4% to 0.2%.
  4. 1.3.04 Aug 2026
    • New frame-budget scheduler — scripts that overrun are suspended and resumed rather than dropped.
    • Deterministic replay: a recorded session replays frame-for-frame with drift reporting.
    • Breaking: rt.run() is replaced by rt.attach():step(). The old call warns for one more release.

Something not working?

Setup logs live in ~/.local/state/cocktail/setup.log. Paste one into the Discord support channel and an engineer will pick it up.

Open DiscordTroubleshooting docs