apps. Just always open the app and then the driver. If you close the app,
  close the driver.
* Don't give up your other tools just yet. It's easy to make a mistake that
  the app doesn't recover from when you fix it. Try restarting the app, and if
  it still doesn't work, perhaps you need to fix the initial load. This isn't
  yet a tool you can keep open for months on end. (And I'm ambivalent about
  making it such a tool since your programs might stop working for others.)

  apps.

* I still see driver and the app being driven occasionally crash. When I do I
  try to make things more robust. If you do you'll quite possibly crash again
  if you try to restart. In such a situation you'll have to bump down to
  editing the underlying version files by other means. See [representation.md](representation.md)
  for details of the underlying representation on disk.
* Given the above issues, both this driver and its client freewheeling app
  benefit from being launched in terminal windows rather than by being clicked
  on in a desktop OS.