This page is for the
nullStack65/t3codefork. Official T3 Code installs and updates come frompingdotgg/t3code; see install.md for those.
Fork builds are published on the fork's GitHub Releases. Download the artifact for your platform and install it; nothing here needs Node, npm, or a compiler.
- Download
T3-Code-<version>-x64.exeand run it. It installs per user and upgrades an existing T3 Code install in place. - For the WSL backend, install WSL 2 and a distro, then pick it in Settings → Connections. The installer already contains the matching Linux runtime, so no separate download is needed.
- The fork also publishes
t3-<version>-win32-x64.zip, a self-contained Windows CLI archive fort3outside the desktop app.
- Download
T3-Code-<version>-x64.dmgand copy the app to Applications. - The fork build is unsigned unless the maintainers signed it. If macOS refuses to open it, right-click the app and choose Open once.
- macOS has no fork
t3CLI archive; run the desktop app, or build the server from source.
Download the self-contained runtime archive and extract it, or install with the fork installer:
curl -fsSL https://raw.githubusercontent.com/nullStack65/t3code/main/scripts/install.sh | shThis puts t3 in ~/.local/bin. Set T3CODE_CHANNEL=nightly only if you know
why; fork releases are plain stable versions. T3CODE_RELEASE_REPOSITORY and
T3CODE_RELEASE_BASE_URL exist for mirrors.
Download the newer artifact and install it over the existing one. Your settings, sign-in, pairings, projects, and databases are preserved.
- Fork releases do not enable automatic desktop updates yet; install the new Windows or macOS artifact by hand.
- On Linux,
t3 updateand the installer download the newer fork archive. - Intel macOS updates by downloading the new DMG; in-app macOS updates are not supported for unsigned fork builds.
The fork publishes linux-x64 and win32-x64 CLI archives. Other
platform/architecture combinations fail with a clear message instead of
downloading a missing asset.
If you are coming from a build that had no update feed, this first release-managed install is the migration: install it once by hand, and later updates can follow the fork release channel.