It's sort of what I'm doing already -- using emacs-server to provide portable persistent sessions on top of a bunch of terminals, agents and editor buffers.
It's a 1% effort on my part and super janky and super me-specific -- if somebody put a small fraction of the effort into it that others are putting into superlogical and the other alternatives listed here, it could be awesome....
Yes, but good, standardized developer tooling is valuable.
Postman could’ve also been a “just use CURL and dump to JSON” for example.
I actually am bullish on this. Tmux and ssh are somewhat clunky and probably under utilized by most people. I struggle to find commands, navigate sessions, see history, and so on.
Also in an “agent” based world where you might ask an agent to execute things for you, how do you manage that context well beyond just giving it its own Tmux session to drive?
It’s a good idea, and I’m surprised no one’s built it sooner.
Emacs is downright friendly compared to git & tmux IMO.
Also, interesting permission problems. Are you going to allow a remote server owned by someone else have shell access to all of your computers? Are they allowed to train an LLM from all the things you type?
can't wait for more details!
What's your approach?
Still a lot of big problems like latency so I’m not too happy with the current design. It’s a LOT of state to replicate, and obviously things get problematic when an agent was working on a project on machine A but then ends up on machine B which doesn’t have that project directory around at all. So the agent needs to re-orient itself to figure out what happened. Still pretty fun to play with.
Still very interested. Especially if you will go further than terminal - multiplexer for window environment, not just in terminal
https://upload.wikimedia.org/wikipedia/commons/3/31/Adobe_Fl...
This is going to change so many things if it starts getting adopted.
