A Terminal Protocol for Program Status (OSC 7501)

(mitchellh.com)

31 points | by mfiguiere 1 day ago

2 comments

  • flopsamjetsam 23 hours ago
    Brings back to mind the old IBM 3270 terminal status line (everything old is new again :). Actually think this is quite a good idea.
    • kevin_thibedeau 2 minutes ago
      It's a product of the scope limited interface granted to agents. They get a terminal stream so everything goes into the stream. Piling on more in-band signaling is just going to become a security nightmare. It would be better to have a safe way to query process state that can be locked down as needed.
    • paaloeye 5 hours ago
      > Actually think this is quite a good idea.

      That's what I thought in the beginning. Once I read the spec to the end, it's clear to me that it's overly specific to one use-case — TUI AI agents.

      E.g. `kind := permission | question | auth` doesn't make much sense anywhere outside of that use case. The list goes on...

      I also found comms around it super muddy, AI agent use case is mentioned but deceivingly watered down with other use-cases.

      Overall, that spec is no where close to Kitty/Kovid's level. It's super sad, since mitchellh's work is usually super high quality.

      I hope the community will push back and the spec will get better.

      • cpuguy83 19 minutes ago
        A cli asking for a password is a pretty normal thing, I think?
  • rauhl 1 day ago