Version 0.4d just released has an option for that. In GUI mode you don't even have to go to job manager to kill them all - simply closing the application in GUI mode will terminate all active jobs since it calls an exit procedure to do just that. In Windows however if you kill the job from Task Manager there is no detectable signal sent to Perl that I can trap to call the exit procedure. In UNIX there is a way to trap kill signals, but not in windows from Task Manager from what I've found, so I don't see a way of doing this. The only way I can trap a signal in Windows it is if you run script from a command window and use Ctrl-C to stop execution. In version 0.4c I already added file cleanup options to the config so you can enable those now for automatic file cleanup. I'll look into it - probably the logic will be if the "auto.history" file already exists then add entries to it as jobs are processed from the GUI. I can add title names to the auto.history file, though I was trying to keep entries as short as possible since over time that file can grow to be pretty large.