You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue for the next release of macOS Golden Gate (v27), announced on Jun 8, 2026.
TLDR STATUS: Ghostty (Tip Channel) works fine on macOS Golden Gate. There could be minor visual glitches here and there. The major work involved for this meta issue is adapting new features for macOS Golden Gate.
This issue will be closed once tip has all known issues resolved with the latest macOS release. We'll probably close this issue at some point along the way during the beta process and not wait for the final final release. I find that usually any breaking changes/bugs for app developers get cleaned up a few betas in while the OS is still ironing out its own issues.
At the time of writing, we're on 1.3.1, which has some known issues that are already being resolved on main branch.
If you're running a macOS beta and want Ghostty to work with the new features, you should use the tip releases (a beta for a beta, if you will).
@trag1c any way to push the release forward and release a v1.4.1 later if there is other stuff that needs to be refined? This is a breaking fix that makes some of the best parts of Ghostty unusable for anyone that updates, which we're all encouraged to do by Software Update now.
I'm sure the release process has too much momentum to change course for the upcoming release. It'll come when it does, and that will resolve macOS 27.
But I did have to move to the tip releases to be able to use Ghostty tabs on the release version of macOS 27. Tabs are essential to my terminal workflow, so for me the stable release didn't really "work fine" after upgrading macOS. FWIW, I understand quirks and glitches; IMHO, the tabs bug was far more than that, and it was noted as far back as July.
In general, I prefer to stay on stable versions, and I wasn't able to do that here while continuing to use Ghostty after upgrading macOS this year.
So I want to raise a couple of questions for future years:
Could the "works fine" assessment noted in this issue's writeup be more conservative/inclusive?
Could the release approach aim for an OS-specific point release closer to the macOS release date?
I understand that this requires up-front work and planning/execution bandwidth that maintainers may not have. That's a suitable argument against why not to do any of this. In that case, a note that this is deliberate would help my assessment of how to adopt Ghostty, and/or which release train to follow.
(I'm not sure if this the right place to raise this discussion--if there's a better spot, please let me know!)
Reacted by Pauline, IsaacInsoll, Ahmed Hassan, Markus Brandt, Cameron Ball, Sean Farrell, Roman Kotenko, Ferdinand Keller, 499602D2, Jack and 1 more
The fact that the stable Ghostty release still has broken tabs a full month after MacOS 27 has been officially out (not including the many months of Betas) shows a clear lack of care to the hundreds of thousands of users of this terminal. Especially when a fix is already in the non-stable versions. Agree with @bmulholland that this needs to be handled better in future MacOS releases.
Reacted by Mathias Hellsing, Kristian Pennacchia, Ferdinand Keller, Ilker Guller, Hugo van de Vliert and José Santos
@bo2themax Thanks for all the work, looking forward to the release. I notice this was closed without comment on my discussion for future handling of macOS releases. Where's a better place to raise that?
@bo2themax Thanks for all the work, looking forward to the release. I notice this was closed without comment on my discussion for future handling of macOS releases. Where's a better place to raise that?
Hi, we'll do our best to fix issues raised because of macOS releases as soon as possible. That's what we did and will keep doing. But this is a volunteer project, so sometimes the stable release will not go exactly as planned.
For users that have issues with the current stable release (1.3.1), they can always switch auto-update-channel to tip, which is also where the next stable release comes from, and switch back to stable if they don't want frequent updates.
I hope this answers your questions.
For all the other questions, you can always look up the existing discussions, if none, you can create one there.
Reacted by Cameron Ball, Brendan Mulholland, YoungHwi and Ashirbad
Activity
macOS: disable liquid class explicitly for layers in icon (#12999)
dj-skn commentedon Jun 22, 2026
bo2themax commentedon Jun 22, 2026
dj-skn commentedon Jun 22, 2026
tabsstyle works correctly after the first public release of Golden Gate #13070bo2themax commentedon Jun 22, 2026
shikiroot commentedon Jun 24, 2026
Switch Ghostty auto-update channel to tip for macOS 27 beta
macos-titlebar-style = hiddenhides top lines #13390drewwells commentedon Sep 15, 2026
5 remaining items
conoremclaughlin commentedon Sep 26, 2026
@trag1c any way to push the release forward and release a v1.4.1 later if there is other stuff that needs to be refined? This is a breaking fix that makes some of the best parts of Ghostty unusable for anyone that updates, which we're all encouraged to do by Software Update now.
bmulholland commentedon Sep 28, 2026
I'm sure the release process has too much momentum to change course for the upcoming release. It'll come when it does, and that will resolve macOS 27.
But I did have to move to the tip releases to be able to use Ghostty tabs on the release version of macOS 27. Tabs are essential to my terminal workflow, so for me the stable release didn't really "work fine" after upgrading macOS. FWIW, I understand quirks and glitches; IMHO, the tabs bug was far more than that, and it was noted as far back as July.
In general, I prefer to stay on stable versions, and I wasn't able to do that here while continuing to use Ghostty after upgrading macOS this year.
So I want to raise a couple of questions for future years:
I understand that this requires up-front work and planning/execution bandwidth that maintainers may not have. That's a suitable argument against why not to do any of this. In that case, a note that this is deliberate would help my assessment of how to adopt Ghostty, and/or which release train to follow.
(I'm not sure if this the right place to raise this discussion--if there's a better spot, please let me know!)
bluekeybo commentedon Oct 3, 2026
The fact that the stable Ghostty release still has broken tabs a full month after MacOS 27 has been officially out (not including the many months of Betas) shows a clear lack of care to the hundreds of thousands of users of this terminal. Especially when a fix is already in the non-stable versions. Agree with @bmulholland that this needs to be handled better in future MacOS releases.
bo2themax commentedon Oct 7, 2026
We have fixed all the sub issues in the main branch, closing it.
bmulholland commentedon Oct 8, 2026
@bo2themax Thanks for all the work, looking forward to the release. I notice this was closed without comment on my discussion for future handling of macOS releases. Where's a better place to raise that?
bo2themax commentedon Oct 8, 2026
Hi, we'll do our best to fix issues raised because of macOS releases as soon as possible. That's what we did and will keep doing. But this is a volunteer project, so sometimes the stable release will not go exactly as planned.
For users that have issues with the current stable release (1.3.1), they can always switch
auto-update-channeltotip, which is also where the next stable release comes from, and switch back tostableif they don't want frequent updates.I hope this answers your questions.
For all the other questions, you can always look up the existing discussions, if none, you can create one there.
bmulholland commentedon Oct 10, 2026
Thanks for the answer, much love, thanks for all the work on the project :)
bluekeybo commentedon Oct 27, 2026
1.4.0 released today fixed this, thanks!
ludcl commentedon Oct 28, 2026
Yes, but the middle click to paste selected text is broken now and we can't open new issues.
I'm reverting to the previous version now :(
trag1c commentedon Oct 28, 2026
Because the flow is to use discussions :-)