Good tool (CW), wrong task.
CiscoWorks is a gret set of tools. Sometimes, though, I believe it's easier to use a more simple tool for such a simple task.
For instance, if your are on a Unix platform, why not just open up a shell, use 'script' ('man script' for optional arguments such as how to redirect output to a custom file name) to record your session and issue the 'sh tech' command? With a little more coding, you could even script a set of commands to call a series of devices up, issue a 'sh tech' on each and save the resultant outputs to individual files.
Similarly, if you are accessing your devices remotely using a Windows telnet or ssh client (such as PuTTY), simply turn on logging for your session and, voila, you have a text log.
Note that if all you want is a set of running configs, CW already stores these down in the shadow archive file structure on your CW server.
