Open-source Coding Agent Pi has formally added support for OSC 7501 in version 1.1.0, according to a BlockBeats brief. The protocol was recently proposed by Ghostty author Mitchell Hashimoto and is designed to let applications explicitly report their state to a terminal, instead of leaving the terminal to infer that state from screen output.
Pi checks whether a terminal supports OSC 7501 when it starts and only sends status updates after support is confirmed. The agent reports "working" while it is running or compressing context, "blocked" when user action is needed for a dialog or login, "done" when a task finishes, and "error" when it hits a non-retryable failure. If a user cancels the task, the state returns to "idle."
The report also says Pi does not send prompts or model outputs to the terminal. Status messages are limited to necessary details such as a session name, a dialog title, or the first line of an error.
Open-source Coding Agent Pi has formally integrated OSC 7501 in version 1.1.0, a terminal status protocol recently proposed by Ghostty author Mitchell Hashimoto.
The protocol lets applications tell the terminal what they are doing directly, rather than forcing the terminal to infer state from what appears on screen.
Pi checks support before sending status
According to BlockBeats, Rex already has preliminary support for OSC 7501. Pi now joins that list with formal support in version 1.1.0.
When Pi starts, it first asks whether the terminal supports OSC 7501. It only sends status messages after that support is confirmed.
Five states are defined in Pi's implementation
Pi reports different states depending on what the agent is doing:
- working when the agent is running or compressing context;
- blocked when user action is required for a dialog or login;
- done when a task is finished;
- error when the agent encounters a non-retryable error;
- idle after a user manually cancels the task.
What Pi does not send
Pi does not send prompts or model outputs to the terminal. The status payload is limited to necessary information, including a session name, a dialog title, or the first line of an error.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
