Great to have other bufs saved!
Have you tested this with multiple tabs and multiple terminal/url windows, etc?

Actually I've found some problems with terminal buffers. The process ID is used to uniquely name each buffer but obviously will not be the same on session restore. It's resulting in terminal buffers being duplicated if they were visible when the session was stored. I have a couple of fixes on the way to solve it. Note that this is also partially an oversight in :mksession!

Other things to check on are any details e.g. ssh sessions, current pwd's of the terminals, etc....
If any ol' terminal session is all that's needed e.g. for pane layouts, then it's simple, but there are itsy-bitsies to watch for.
Agree on the pros and cons of Vim's mksession, which has had series of changes in patches and versions. :|

The terminal buffer name encodes the starting working directory and the command line to run. I don't think vim has any way of recording all the environment variables at the time a terminal was created but some can be explicitly overridden on the command line, which will be preserved.

Hmmm... I just tried to use your latest modified workspaces setup and it reloads the workspace with file buffers named after the terminal sessions. It names them as I loaded them, i.e. with the +cmd such as ssh server or cd dir.

If this works on your end, perhaps some vimrc settings are diff between us?
I so hope it's that simple, as I'll use this terminal reload immediately.

My vim version is 8.0, patches: 1-1802

Ah - I was unaware vim-8 had added an immature, optional terminal feature; I was using neovim. There must be some significant differences between the two implementations. I'm going to have to compile vim from source and experiment to see how it works.

Hello @domsekotill , any progress on this? @jyscao, would skipping terminal buffers be an option?