Termdock Issue Reports & Fixes Thread
by•
Hi everyone
I’ve received reports from x64 users that the Terminal can’t start. I want to confirm whether this issue affects all x64 environments or only certain setups. I don’t have an x64 machine on hand, so your feedback is very helpful.
The root cause: our package shipped with the arm64 build of node-pty by default. On x64, node-pty isn’t recognized, which causes the Terminal to fail at startup.
If you run into any issues, please comment here or open an Issue on GitHub.
105 views


p/reso
p/runevr
p/producthunt
p/google-cloud-platform
p/many-displays
p/slotify-2
p/airuncode
p/ai-context-flow
p/kodlo
p/aperture-7
p/raycast
p/lasso-11
p/kuc-kuc
p/dino-kids
p/supabase
p/jev
p/offiai
p/murror
p/dex-by-exmergo
p/htmldrag
Replies
I’ve already applied a fix, and testing the x64 build through Rosetta shows terminal input works and connects correctly. The update is in 1.3.1 — just restart the app to update.
Here’s a more casual, human‑sounding update for everyone.
Termdock v1.3.2 — Heads up
We found why some Intel Macs couldn’t open the Terminal: the app was loading the arm64 pty by default. That’s fixed.
Pty fix: The app now picks the right binary at runtime for both x64 and arm64.
Notarization: All macOS builds are properly signed and pass Gatekeeper.
Still stuck on x64? You’ll see an error log dialog. Hit “OK” and paste that log into the GitHub issue so I can dig in.
Grab the right DMG for your Mac (Intel or Apple Silicon). If anything still breaks, send the log—I’ll follow up. Thanks!