[iconara]

On the Example Script page (https://iterm2.com/python-api/tutorial/example.html) it says that the script communicates with the application using websockets ("The underlying implementation uses Google protobuf and websockets"). This makes me think that it could support other languages and ways of scripting it in the future.

[bitwize]

Wait, web sockets? Why not regular old sockets? Why not restrict it to Unix domain sockets so that only authorized users can talk to the iTerm instance?

[tdrd]

Maybe so folks could build web UIs to interact with a local instance? Can't do raw TCP/UDP from a web browser.

[bitwize]

Then write a bloody wrapper.

Controlling my terminal emulators through a browser is like managing processes with Doom: something that, while interesting and certainly shouldn't be precluded, I am unable to think of a use case where I would actually do it. Making web sockets the scripting interface for a program that in most cases you do NOT want to actually expose to the web a) makes no sense; b) is a security incident waiting to happen.

[booi]

Manage processes with Doom you say...

[bitwize]

Yes, I was specifically referring to this: https://www.cs.unm.edu/~dlchao/flake/doom/chi/chi.html

[tehno]

Or Kubecraft :) https://www.youtube.com/watch?v=A4qwsSEldHE