The #hex1b terminal stack includes its own terminal emulator which maintains what it things the terminal state is even if you are connected to a real emulator - so conceptually this is just projecting that terminal state onto a web canvas.

At this point there are lots of question marks around perf.

Experimenting with the idea of #hex1b having its own web-based terminal renderer that uses WebGPU. All of the terminal state stays server side with the Hex1bTerminal instance, but state updates are transmitted over the wire via a websocket to some JS code that renders onto canvas.