Here's an interesting anomoly: If you have started the GUI, itestcli can use the workspace, no problem. But if you have started itestcli, the GUI won't let you open the workspace! Is there any workaround for this?
Being as the test reports are only available in the workspace, this causes a serious problem when you need to hop onto your test controller and figure out why last night's test failed, since today's is already running. I guess you could leave the GUI running all the time, but--as I mentioned elsewhere--it gets slow after a while.
I haven't figured out a real good way to mix the whole workspace concept with batch jobs. I'm open to suggestions as to how to do this.