[BlueBerry2001]

That would be a really interesting direction, and I agree it fits the idea well.

Right now Cate is a local desktop app because we wanted the first version to work closely with local projects, shells, files, node-pty/xterm, browser panels, Monaco, git worktrees, etc.

A self-hosted web version would need a different architecture: a backend that owns the PTY sessions, keeps them alive when the browser disconnects, handles auth/security, and syncs the canvas state to the client. Definitely possible, but a bigger shift than just “put the current app in the browser”.

Long term I think remote/headless workspaces and reconnectable sessions would make a lot of sense.