Repository navigation
Releases
ghostty 1.4.0
Changed
- Standard semantic versioning. Previous releases used
1.3.1-paste.N. In semver the-paste.Nsuffix is a pre-release segment, so semver-based comparisons sorted every released fork build before1.3.1, and the fourth counter said nothing about whether a release added features or fixed bugs. This release moves to plainMAJOR.MINOR.PATCH: a minor bump on top of the upstream v1.3.1 baseline because it adds the builtin default config and the fixed certificate signing. Later releases follow semver — features bump minor, fixes bump patch, breaking changes bump major. - The build now takes its version from
VERSION.-Dversion-stringandCFBundleShortVersionStringwere hardcoded to1.3.1, so the app's About box disagreed with the tag and the release. Both values now come fromVERSION;CFBundleVersionstill uses the commit count and keeps increasing.
Notes
v1.4.0contains everything from1.3.1-paste.6; the1.3.1-paste.*tags and releases stay as history.v1.3.1-paste.5remains a pre-release because its asset could not launch.
ghostty 1.3.1-paste.6
Fixed
- The certificate-signed build launches again. The signing step enabled the hardened runtime, and hardened runtime turns on library validation: a loaded dylib has to share the main executable's Team ID. A self-signed certificate has no team ID, so dyld refused to load
Sparkle.framework(mapping process and mapped file (non-platform) have different Team IDs) and the app died on launch. The signing step no longer passes--options runtime. This fork is not notarized, so the hardened runtime bought nothing, and the earlier ad-hoc builds never used it either.
Notes
- The asset published with
v1.3.1-paste.5could not launch. That release is now marked as a pre-release and kept for the record only — install this version instead. - Verified on the released build:
flags=0x0(none),Authority=Ghostty Fork Self-Signed,codesign --verify --deep --strictpasses,ghostty +show-configprints the builtin defaults and+validate-configis silent. The designated requirement is identical to the paste.5 build, so the Accessibility identity does not change.
ghostty 1.3.1-paste.5
Warning: the
Ghostty.app.zipattached to this release does not launch. The hardened runtime enabled library validation, which rejectsSparkle.frameworkfor a self-signed certificate (no team ID). This release is kept for the record only — install v1.3.1-paste.6 instead.
Compile the default look and feel into the binary, and sign builds with a fixed self-signed certificate.
New: default look and feel compiled into the binary (works out of the box, defaults no longer come from a file anything can rewrite)
- Why: Ghostty takes its entire configuration from files on disk, so the terminal's look has to be rebuilt by hand after switching machines or reinstalling; and any program able to write
~/.config/ghostty/configcan casually change those defaults (the two-way interference happened with cmux reading the same file — see Issue #24 and xhqing/cmux#70). - What changed: (1) Added
src/config/config-builtin.ghostty(9 look-and-feel defaults: theme, font family, font size, cursor, shell integration), loaded first via@embedFileinConfig.loadDefaultFiles()— it is the lowest-priority layer, since every user config file (XDG / App Support) loads after it and naturally overrides it; whenconfig-default-files = falsethis layer is dropped together with the user configs, so the semantics are unchanged. (2) The built-in config carries only machine-independent values: window size / position and everykeybind(the Quick Terminalglobal:hotkey, thesuper+vimage-paste patch) still belong to the user config file. (3) Added Zig unit tests: the built-in file must parse, and a user config loaded later must override it. - Boundaries: (1)
theme = GitHub Dark Defaultrelies on the theme directory bundled with the app (Contents/Resources/ghostty/themes;emit-themesdefaults to true, so no extra packaging is needed). (2) A machine that has never created a config file still gets the commented template on first launch (existing behavior); the built-in values take effect on top of that template.
Changed: builds are signed with a fixed self-signed certificate, so the Accessibility grant no longer dies with every build
- Why: This fork's artifacts were ad-hoc signed, and macOS TCC matches the Accessibility grant for an ad-hoc signed app by its signature hash (cdhash) — every rebuild changes the hash, the system treats it as a different app, and the previous grant is silently revoked (measured 2026-09-22: right after installing a new build,
osascriptinside the terminal failed withnot allowed to send keystrokes (1002), and the only recovery wastccutil resetplus re-granting by hand; Issue #2). - What changed: (1)
build.ymlgained a certificate-signing path: it imports the fixed self-signed certificate from secrets (a.p12) into a throwaway keychain, marks trust for the code-signing policy only, signs the nested Sparkle components one by one and then the app itself, verifies the signature and prints the designated requirement, and deletes the keychain when the build finishes. When the secrets are unavailable (pull requests from forks) it falls back to ad-hoc so CI still produces artifacts. (2) AddedSIGNING.mdcovering what the certificate is for, the secret names, and why it must not be casually regenerated. (3) Removed the upstream leftover workflows:vouch-check-pr.yml/milestone.yml(which usedpull_request_target), thevouch-*family, andrelease-tag.yml,release-tip.yml,publish-tag.yml,flatpak.yml,snap.yml,nix.yml,test.yml,update-colorschemes.yml(which depended on upstream's Namespace runners, Nix, its own CDN and minisign) — in this repository they either always skip or only ever fail, sobuild.ymlis now the single CI workflow. - Boundaries: (1) The self-signed certificate is not in Apple's trust chain and the app is not notarized, so Gatekeeper still requires a manual allow on first launch (same as ad-hoc, not a regression). (2) Once the certificate is in use, do not regenerate it — changing it means changing the signing identity, and every machine has to re-grant Accessibility once. (3) Builds from this branch are the paired test:
codesign -dvshould report the certificate identity (Authority=Ghostty Fork Self-Signed) instead ofSignature=adhoc; the Accessibility grant is re-tested after installing the next Release.
ghostty 1.3.1-paste.4
Closing the last terminal window now quits Ghostty, so the Dock icon no longer keeps its dot.
Changed
- Closing the last window quits the app.
quit-after-last-window-closednow defaults totrueon every platform (upstream keeps itfalseon macOS). A running-but-windowless Ghostty looked identical to one that still had windows at a glance — the Dock dot was there either way — so every close needed a manual re-check. Writequit-after-last-window-closed = falseto get the upstream macOS behavior back. Surfaces with a running process still ask for confirmation before closing, and a hidden Quick Terminal window does not block the quit. - Build artifacts expire after 7 days instead of 90 (
retention-days: 7), and the dailyClean Artifactsworkflow is gone — retention is now handled by GitHub itself. Artifacts still cover on-device verification and pulling a binary when releasing. - Repository housekeeping. Agent-specific files stay out of the project per the 2026-10-12 policy, and this repository's
.piis a real directory referencing the agent resource folders instead of a symlink into the agent project.
Fixed
Clean Artifactsno longer fails every day. It deleted artifacts older than a week through the Actions API, which needsactions: write, while the repository default isread— so it returned 403 as soon as the first artifact aged out (and mailed aRun failednotice daily since 2026-09-28). The workflow is removed.
Install
Download Ghostty.app.zip below, unzip it, and replace the existing app in /Applications.
ghostty 1.3.1-paste.3
Agent-exclusive files removed; the upstream development guide moved to a regular doc.
Changed
- Per the 2026-10-12 policy, the agent-exclusive files and directories (
.claude/CLAUDE.md,AGENTS.md,.agents/) are removed; the upstream development guide now lives inDEVELOPMENT.md.
ghostty 1.3.1-paste.2
What this is
Personal fork of Ghostty, based on upstream v1.3.1, carrying a single macOS feature:
Cmd+V pastes clipboard images as a temp-file path. Screenshots captured straight to the clipboard (Cmd+Shift+Ctrl+4) previously did nothing on paste — the clipboard holds only image data, no text and no file URL. This fork writes the image to $TMPDIR/ghostty-paste-<UUID>.png (TIFF converted to PNG) and pastes the escaped path, so TUI apps (Claude Code, pi, …) receive it as an image path. Existing paste behavior is unchanged: file URLs still paste as paths and text still pastes as text.
No terminal code changed in this release — the app is built from the same source as v1.3.1-paste.1. This version packages repository-level work only:
Added
- Project standard files: a new
VERSIONfile;LICENSEconverted toLICENSE.md(the upstream copyright line is preserved, the fork's own line is added, and the redundant extensionlessLICENSEis removed); README badges (License / Version / Type), an English + Simplified Chinese README pair, and a License & Attribution section;.commit-cache.mddetection cache; bilingual GitHub repository description with topics.
Changed
mainis protected: every change lands through a pull request that passes the requiredbuild-macoscheck and is squash-merged automatically. The paths filter was removed frombuild.ymlso documentation-only pull requests still run CI and can satisfy the required check.- This repository is now an independent fork: the fork relationship with
ghostty-org/ghosttywas removed on 2026-09-20,mainwas reset to the patch line (v1.3.1 + patch + docs), 7 leftover upstream branches were deleted, and the repository description was updated.
Install
Download Ghostty.app.zip, unzip, and replace /Applications/Ghostty.app. Existing config in ~/.config/ghostty is untouched.
Note: the app is ad-hoc signed (no Apple Developer certificate). If macOS refuses the first launch, allow it in System Settings → Privacy & Security.
Build
Built by GitHub Actions (build.yml): Zig 0.15.2 + Xcode 26.2 (the upstream v1.3.1 toolchain), universal binary (x86_64 + arm64). Fork-specific changes are tracked in CHANGELOG.md.
v1.3.1-paste.1
What this is
Personal fork of Ghostty, based on upstream v1.3.1, adding a single macOS feature:
Cmd+V pastes clipboard images as a temp-file path. Screenshots captured straight to the clipboard (Cmd+Shift+Ctrl+4) previously did nothing on paste — the clipboard holds only image data, no text and no file URL. This fork writes the image to `$TMPDIR/ghostty-paste-.png` (TIFF converted to PNG) and pastes the escaped path, so TUI apps (Claude Code, pi, …) receive it as an image path.
- Existing paste behavior is unchanged: file URLs still paste as paths, text still pastes as text. The image fallback only kicks in where upstream silently pasted nothing.
- Same idea as cmux (host-layer) and Warp (GUI-layer); implemented in the terminal's own clipboard read path.
- Approach from ghostty-org/ghostty#11571 (auto-closed by the vouch bot), independently verified end to end.
Install
Download `Ghostty.app.zip`, unzip, replace `/Applications/Ghostty.app`. Existing config in `~/.config/ghostty` is untouched.
Note: the app is ad-hoc signed (no Apple Developer certificate). If macOS refuses first launch, allow it in System Settings → Privacy & Security.
Build
Built by GitHub Actions (build.yml): Zig 0.15.2 + Xcode 26.2 (the upstream v1.3.1 toolchain), universal binary (x86_64 + arm64). Fork-specific changes are tracked in CHANGELOG.md.