(macOS, fish) Process name remains after exit if suspended at least once

[mnemnion]

Issue Description

As indicated, this is on macOS with fish shell.

There is a similar issue which was due to disabling shell integration. My Ghostty config doesn't show any evidence that I have done likewise, and I am nearly positive I have never done so.

At issue: when running, e.g., nvim, and exiting normally, the tab title returns to showing the directory. However, if I enter, ^Z suspend (which I do very frequently), then re-enter, then quit, it retains nvim in the title.

Which is interesting! Because I invoke nvim with vi (vi not?), and it says vi ~blah during the session, but nvim $argv etc after it.

So this is very likely a fish shell thing, and I am able to use the difference to determine what I'm trying to find out, which is if I have jobs open in any of my tabs. If, that is, they're in the foreground; my suggestion that Ghostty support background jobs in titles got panned, although frankly I think that was hasty. I don't see how it's less important than the little bell emoji which shows up if BEL was sent, but then, I use jobs, so I would think that. Anyway. Not why I'm here!

But that's just a happenstance, because I use a fish function to invoke Neovim. When I use nvim blah.txt, suspend, resume, and exit, I get nvim ~/directory as a title, so it's not because I'm using a fish function either. type nvim says the location, so it's not any sort of alias. Just to be thorough.

Expected Behavior

Exiting a job should have the same effect on the title, namely, clearing the job info, whether or not the job was suspended during execution.

Actual Behavior

Something based on the invocation of the job is left in the title.

Reproduction Steps

• Open Ghostty (on, at least, macOS)
• fish if not in fish already
• Added: if you have a fish_function in .config/fish/functions, stash it elsewhere prior to launching the shell.
• nvim somefile
• ^Z
• fg
• :q!
  The title bar should still say nvim.

Ghostty Logs

Looks useful!

Filtering the log data using "subsystem == "com.mitchellh.ghostty""
Timestamp                       Thread     Type        Activity             PID    TTL
2026-01-02 06:55:12.926065-0500 0x1da4     Info        0x0                  642    0    ghostty: [com.mitchellh.ghostty:osc] unknown semantic prompts option: cmdline_url
2026-01-02 06:55:13.204873-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] ignoring CSI t with unimplemented parameter: ESC [  { 8, 71, 130 } t
2026-01-02 06:55:19.602421-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command__struct_18710{ .exit_code = 0 } }
2026-01-02 06:55:19.602477-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC command: end_of_command
2026-01-02 06:55:19.602859-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command__struct_18710{ .exit_code = 0 } }
2026-01-02 06:55:19.602903-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC command: end_of_command
2026-01-02 06:55:19.602924-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command__struct_18710{ .exit_code = null } }
2026-01-02 06:55:19.602934-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC command: end_of_command
2026-01-02 06:55:19.751589-0500 0x1da4     Info        0x0                  642    0    ghostty: [com.mitchellh.ghostty:osc] unknown semantic prompts option: click_events
2026-01-02 06:55:27.271978-0500 0x1da4     Info        0x0                  642    0    ghostty: [com.mitchellh.ghostty:osc] unknown semantic prompts option: click_events
2026-01-02 06:55:27.851622-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] ignoring CSI t with unimplemented parameter: ESC [  { 8, 71, 130 } t
2026-01-02 06:55:27.852426-0500 0x1da4     Error       0x0                  642    0    ghostty: [com.mitchellh.ghostty:stream] ignoring CSI t with unimplemented parameter: ESC [  { 8, 71, 130 } t
2026-01-02 06:55:30.279276-0500 0x1da4     Info        0x0                  642    0    ghostty: [com.mitchellh.ghostty:osc] unknown semantic prompts option: click_events

Ghostty Version

Ghostty 1.2.3

Version
  - version: 1.2.3
  - channel: stable
Build Config
  - Zig version   : 0.14.1
  - build mode    : builtin.OptimizeMode.ReleaseFast
  - app runtime   : apprt.Runtime.none
  - font engine   : font.main.Backend.coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue

OS Version Information

Sequoia 15.6.1

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

# None needed

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[mnemnion]

Relevant update: I finally went ahead and implemented the jobs icon fish_title based on advice in that thread (thanks btw), and a side effect of that is that the behavior described here is no longer evident.

So addendum: having a custom fish_title function is sufficient to not reproduce this. I didn't have one of those, this suggests to me that something in how Ghostty is integrating with fish is doing it. I'll add "don't have a fish_title function" to the repro list.

[mitchellh]

I don't believe this is a Ghostty bug. We set the title based on what running programs (Neovim, Fish, etc.) tell us. We don't set the title manually unless it is blank, in which case set it to "Ghostty." I think all of this is downstream.