There is actually no way to inspect the "history" of commands that have been sent to the underlying CLIPS engine. In fact, unlike similar projects, PyCLIPS does not limit its interaction with CLIPS to sending commands to the engine. What PyCLIPS mostly does is to call the intrinsic low-level CLIPS API to access and modify the engine state. However the underlying engine keeps its ability to produce a possibly (even too densely) detailed trace file. See the documentation for the DebugConfig object in the manual in order to learn how to produce a trace file with the desired detail, and the CLIPS manual if you are uncertain about what entities or actions can be "watched" and for what purpose.