Ghostty author proposes OSC 7501 a terminal protocol, already implemented in libghostty and Rex

Article

Ghostty author proposes OSC 7501, letting programs tell the terminal what they are doing

Beating AI news flash: Mitchell Hashimoto, Ghostty author and HashiCorp co-founder, has proposed a new terminal protocol OSC 7501.

Once programs such as Claude Code, Codex, and Terraform are running, external tools often do not know whether they are working, waiting for input, or already finished, and can only guess.

Tools such as Herdr currently read the terminal screen, window title, and process, then use rules to determine the agent's state. Mitchell said, for example, that Herdr maintains 16 rules just to identify Claude Code; over the past 3 months, these rules have been changed approximately 10 times. A change to Claude Code's loading animation could require a new adaptation. He also said that he found 250 Agent orchestration tools, many of which are repeatedly solving similar problems.OSC 7501's approach is to have programs report their own status. A program can tell the terminal that it is idle, working, waiting for the user, completed, or in error, and can also attach progress information and explain why it is waiting. For example, when Claude Code is stuck awaiting permission confirmation, it can directly tell the terminal “I am waiting for authorization,” instead of making Herdr infer this from text and symbols on the screen.

These states are transmitted through the terminal connection that the program is already using, so SSH and containers can also work normally. Existing terminal progress protocols can express only busy, progress, or error states, and do not clearly indicate what the program is waiting for.OSC 7501 fills this gap.

Mitchell has implemented the protocol in libghostty and Rex, and created proofs of concept for Terraform, Claude Code, Codex, and Homebrew through plugins or fork. Integration is not complicated; each implementation is no more than a dozen lines of code. However, whether OSC 7501 can achieve widespread adoption will depend on whether other terminals and programs are willing to adopt it.

Original link https://m.theblockbeats.info/flash/370538

Key points

Ghostty author and HashiCorp co-founder Mitchell Hashimoto proposed the terminal protocol OSC 7501。
The report gives as examples that programs can report idle, working, waiting for the user, completed, or error states, and can include progress and the reason for waiting.
Mitchell Hashimoto said that Herdr maintains 16 rules to identify Claude Code, and changed them approximately 3 times over the past 10 months.
Mitchell Hashimoto said that he found 250 Agent orchestration tools.
The report states that OSC 7501's status is transmitted through the terminal connection the program is using, so it can also work in SSH and containers.
Mitchell Hashimoto has implemented the protocol in libghostty and Rex, and created proofs of concept for Terraform, Claude Code, Codex, and Homebrew through plugins or fork.
The report states that each proof-of-concept implementation consists of no more than a dozen lines of code.

AI-assisted interpretation

The following is analysis, separate from reported facts. Verify important claims independently.

At present, external tools often guess a program's status by reading the terminal screen, window title, and process; interface changes can cause identification rules to fail.OSC 7501's approach is for the program to tell the terminal directly that it is working, waiting for input, completed, or encountered an error, along with the reason for waiting.

Why it matters to readers

If terminals and programs adopt the protocol, tools such as Herdr may no longer need to continuously maintain large numbers of state-detection rules that depend on interface characteristics, and could distinguish more directly whether a program is running or waiting for user input.

Beginners using Claude Code, Codex, or Terraform may in the future find it easier to understand what the program is currently doing and whether they need to confirm permissions or perform other actions themselves.

Risks and unknowns

OSC 7501 Whether
The statements in the article concerning the number of rules, number of changes, number of Agent orchestration tools, operation across SSH and containers, and implementation code size are not independently substantiated by evidence provided here.
It remains unclear whether the existing proofs of concept represent compatibility and stability in real-world environments.

Ghostty author proposes OSC 7501 a terminal protocol, already implemented in libghostty and Rex

Article

AI-assisted interpretation

Why it matters to readers

Risks and unknowns

Related Developments

Related concepts

Keep following

Security Center