OSC 7501 Makes Terminal Agents Legible
Mitchell Hashimoto’s OSC 7501 gives terminal programs a native way to report idle, working, blocked, done, or error states, including permission, question, and authentication waits. Rex turns those signals into session indicators, tab status, and programmable events for monitoring coding agents across sessions. [Announcement](https://mitchellh.com/writing/program-status-osc7501) [Rex docs](https://www.superlogical.com/rex/docs/build/program-status)
Hot take: this is unglamorous plumbing with unusually high leverage—one tiny protocol could replace a cottage industry of brittle spinner, title, and screen-parsing heuristics. Its success now depends less on the specification than on terminals, multiplexers, and agents agreeing to implement it consistently.
- –Reports richer state than basic terminal progress sequences, including why an agent is blocked and optional progress or messages.
- –Uses the existing pseudo-terminal path, making it practical across SSH, containers, and remote sessions without bespoke integrations.
- –Rex keeps presentation separate from the protocol, enabling tab badges, session indicators, mobile alerts, or custom Lua workflows.
- –The protocol is small enough for tools to implement quickly, which helps explain early interest from coding agents and terminal projects.
- –The main risk is adoption fragmentation: a perfect status signal is useless when either the agent or terminal still relies on heuristics.
DISCOVERED
26m ago
2026-11-12
PUBLISHED
28m ago
2026-11-12
RELEVANCE
AUTHOR
AICodeKing