Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Copilot CLI 1.0.86 reliably crashes Ghostty 1.3.1 on macOS; Terminal.app unaffected

未關閉
#4,915 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
macos, node.js, shell

研究方向

Start by reproducing the crash with Ghostty and Terminal.app, then inspect the shutdown EPIPE alongside TERM=xterm-ghostty and the image-storage-limit=0 control. Done means identifying a Copilot-side trigger and a safe fallback, or establishing that the fault belongs in Ghostty; the issue names no source file or test.

由索引模型根據 Issue 內容生成。

描述

triage

TL;DR: Running Copilot CLI inside Ghostty kills the terminal within seconds, five out of five attempts, taking every tab and every child process with it. The exact same command in Terminal.app on the same machine works fine. Copilot's own logs show no panic and no OOM, so the terminal is what dies, but Copilot is a reliable trigger and right now it is unusable in Ghostty.

Environment

  • GitHub Copilot CLI 1.0.86, npm install -g @github/copilot
  • Ghostty 1.3.1 (crashes) vs Terminal.app (fine)
  • macOS 26.6.1 (25G76), arm64
  • TERM=xterm-ghostty, zsh, Node v24.14.0 system / v24.20.0 bundled

Steps to reproduce

  1. Install and authenticate
  2. Open Ghostty
  3. Run any prompt, copilot -p "..." or interactive
  4. Ghostty terminates within a few seconds

Expected: the prompt runs, or fails cleanly.

Actual: the terminal emulator dies and takes the shell, the CLI, and every other tab with it. Work in unrelated tabs is lost.

Control: identical steps in Terminal.app, same machine, same version, same MCP servers, same shell. No crash. That is the part that makes this worth your time even though the fatal fault is on the terminal side.

What the logs show

Copilot looks healthy right up to the end. No panic, no OOM, no abort. The only error:

[ERROR] [shutdown] Failed dispose: PromptMode.stdout (3ms): Error: write EPIPE

Reader gone, so the terminal died first. Child processes exit 137.

Hypothesis I tested and ruled out

Ghostty has an open segfault on terminal reset after displaying an image (ghostty-org/ghostty#5649), and your built in MCP server is the only one of my four advertising base64 PNG icons:

server_info: Implementation { name: "github-mcp-server", ...
  icons: Some([Icon { src: "data:image/png;base64,...", mime_type: Some("image/png") }, ...]) }

My three other MCP servers all report icons: None. So I set Ghostty's image-storage-limit = 0, verified it was live in a freshly launched window, and it still crashed. The image path is not the cause. Recording it so nobody repeats the experiment.

Mechanism: unknown. Something in how the CLI drives the terminal takes Ghostty down and does not affect Terminal.app. I have not narrowed it further.

Why it is worth looking at on your side

  1. Five for five, from a clean install, with no third party configuration required
  2. Ghostty is widely used and the failure is total, not cosmetic. The process dies and unrelated work is lost
  3. There is already a known rough edge between these two (ghostty-org/ghostty discussion #9264, Enter key not registering in your interactive prompts), so the pairing has form
  4. Even if the fix belongs to Ghostty, a capability check or a quieter fallback on your side would unblock users now rather than after a Ghostty release

Happy to run an instrumented build, capture raw output to a file, or grab a spindump.

主要語言
Shell
星號
11.2k
分支
1.9k
平均合併
17 小時 6 分鐘
30 天內合併 PR
5

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/copilot-cli 的其他 Issue

查看 github/copilot-cli 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。