Codex 0.150.0

在終端機同時推進多項任務時，跨任務調度現在變得像通訊軟體一樣自然。

你可以用 @ 標記其他 Codex 任務來直接引用其內容；也能在終端機中請代理（agent，自動替你執行任務的 AI 助手）讀取特定任務、建立新任務，或向進行中的任務傳送訊息。這讓多工協作時不必手動複製貼上歷史紀錄。

想從長篇對話中抽出一小段程式碼或重點時，不用再拿滑鼠在終端機裡吃力選取。輸入 /copy 指令後，介面現在會跳出選擇清單。你可以自由挑選要複製整篇完整回覆、各個獨立的程式碼區塊，或是特定的引用區塊。這讓擷取內容變得更加精準俐落。

終端機裡開了一堆任務卻常分不清內容的問題，現在有了更省心的解法。

未手動命名的終端機任務現在會根據對話自動獲得具描述性的標題；當你想重新命名時，輸入 /rename 指令也會依據當前對話主動建議一段可編輯的標題草稿。這讓你在任務清單中能一眼辨識目標，省去手動打字命名的繁瑣步驟。

閱讀包含超連結的回覆時，終端機畫面變得更加乾淨易讀。在支援超連結的終端機環境下，Markdown 格式的連結會直接顯示為可點擊的簡潔文字標籤；而在不支援點擊的其他終端機中，系統則會完整保留原本可見的網址字串。這樣既能保持排版清爽，又確保在任何環境下都不會遺失網址資訊。

你可以把循環切換權限模式的動作綁定到快捷鍵。權限模式（permission mode，決定系統在執行動作時如何處理確認的規則）會隨著這個按鍵依序切換。

當工作需要換一種確認方式時，使用你設定的快捷鍵，即可在可用的權限模式間循環切換；想再換一種就繼續按下去。

Vim 模式裡有多處要做同樣的文字修改時，現在按下 . 就能重複上一個編輯。Vim 模式（以鍵盤指令操作文字的編輯方式）會把剛完成的編輯動作交給 . 重新執行，不必再次逐字輸入相同變更。

這是 Vim 模式中的編輯重複功能。

任務執行途中突然按暫停時，後續的清理與自訂動作現在能自動接手。

系統新增了 Interrupt hook（掛鉤，特定事件發生時被觸發的小程式）。當進行中的頂層對話輪次被中斷時，這項機制可以自動執行命令列指令，或呼叫 MCP（讓 AI 連接外部工具的協定）處理常式進行收尾。這讓中止操作不再只是粗暴中斷，而能妥善保存狀態或釋放佔用的資源。

匯出診斷日誌排除故障時，機密資訊的外洩風險現在降得更低。系統強化了應用程式伺服器診斷報告中的 credential（登入憑證，證明身分與權限的密鑰資料）遮蔽處理。這次改進精確涵蓋了服務提供者、身分驗證更新以及 attestation（證明裝置與環境合法性的認證欄位）等關鍵資料。當你分享除錯診斷資訊時，這些敏感欄位會被自動遮蓋。

在 Unix 系統（如 macOS 或 Linux 等環境）結束程式時，不再因為背景殘留問題而卡死。以前當已脫離的行程依然佔用終端機，或者輸出緩衝區已被塞滿時，結束程式的流程常會陷入無限等待；現在系統會妥善清理這些狀態並順利退出。這讓每次離開工具時都能乾脆俐落。

When running multiple parallel tasks in the terminal, coordinating across workflows is now as natural as using team chat.

You can now use @ mentions to reference other Codex tasks directly in your prompt. You can also ask agents from the terminal to inspect existing tasks, spin up new ones, or dispatch messages to active tasks without manual copy-pasting.

When extracting a specific snippet or excerpt from a long reply, you no longer need to drag your mouse across terminal text. Running /copy now opens an interactive picker menu. You can explicitly choose between copying the full response, individual code blocks, or markdown blockquotes.

When juggling multiple background tasks in your terminal, identifying what each task is doing is now effortless.

Unnamed terminal tasks now automatically receive descriptive titles based on context. Furthermore, running /rename inspects your conversation history and suggests an editable title proposal, saving you from having to type names manually.

Reviewing responses that contain hyperlinks is now much cleaner in your terminal. On supported terminals, Markdown links render as tidy, clickable text labels. In environments without hyperlink support, the full visible URLs remain intact so you can still read and copy them easily.

You can bind cycling through permission modes to a custom shortcut. A permission mode determines how Codex handles confirmation before an action, and the bound key moves through the available modes in sequence.

When your work calls for a different confirmation approach, press the shortcut you configured to cycle to it.

When the same text change is needed in several places in Vim mode, pressing . now repeats your last edit. Vim mode is a keyboard-command way to edit text; . reruns the edit you just completed, so you do not need to type that same change again.

This is the editing-repeat feature for Vim mode.

When cancelling an active turn midway, automated cleanup and custom actions can now take over immediately.

Codex introduces Interrupt hooks. When an active top-level conversation turn is interrupted, these hooks can automatically run shell commands or trigger MCP handlers, allowing your environment to safely persist state or release held resources instead of abruptly terminating.

Exporting diagnostic reports for troubleshooting is now much safer. Codex has expanded credential redaction across app-server diagnostics. Sensitive data is now automatically masked across provider details, authentication refresh flows, and hardware attestation fields. When you share debug output with maintainers, secret tokens and verification payloads will never leak into log files.

Exiting Codex on Unix systems like macOS or Linux is now fast and reliable. Previously, shutting down could hang indefinitely if detached background processes still held terminal handles or if output buffers were completely full. The shutdown sequence now cleans up detached processes and flushes full buffers properly.