The first incarnation required major resources for every concurrent session since a mini httpd server was started to communicate with every client. In the rearchitecture, individual sessions are attached to UNIX domain sockets which can be disconnected while still maintaining state for individual sessions. The architecture used internally is now much simplified. We will shortly release a simple toolkit to enable construction of similiar interfaces to programs which maintain state. Parts of wysh are still to be completed, but it is now able to deal more comfortably with a large number of concurrent sessions.
Documentation still needs to be written, but the basic architecture is now stable.
Any further development will occur in the context of the new framework for stateless handling of 'sessions'. The old syntax has been broken now, to prevent problems during later stages of development. Later versions of wysh may include the use of further variables in the initialisation of a 'session'. These may be used to control presentation, starting state or other aspects of the software. Well, I said I'd never do it, but here it is.