If the gCLI could be logged like chats and loaded into the browser via quick button that would work (though I wouldn't want the gCLI to be saved from day to day like chat logs... way too many files of mostly repetitive info) and, if the gCLI worked like chat, wouldn't that help alleviate the problem of ambiguity that was had with the amount of memory dedicated to the gCLI history? I don't actually really know how it works, but chat seems to be logged as far back as one is logged in without problem so I'd assume similar would be possible for the gCLI.
Slight veer. Much of what is written to the gCLI is also written to the Session Logs so I'm not sure what "though I wouldn't want the gCLI to be saved" is supposed to mean since it already is. If I were going to make a FR I would ask that
everything written to the gCLI be "unHTMLed" and then written to the session log.
My recollection from tweaking the buffer size is that the gCLI and Chat share much of the same underlying classes so I'm not sure that it is really true that the gCLI does not work like Chat. A specific example where that is true might suggest some easy code changes to make them work the same or provide reasons why they should be different. By the same token I'm pretty sure, as the person who did it, that the buffer sizes for Chat and gCLI are the same so if there is a different experience between the two as far as scrolling or how far back things go then it is almost certainly related to data volume and not code.
In Ye Olde Ancient Tymes many tools that displayed scrolling output would let you pause and resume scrolling using ctrl-S and ctrl-Q (IIRC). However before multi-threading that would sometimes pause the underlying process. Inevitably, the solution was to tee the output to a second process and pause that process or write everything to a file and use tail -f (again, IIRC).
Since KoLmafia is multi-threaded I wonder if this should really be a FR that it be possible to pause all scrollable buffers and scroll back without pausing the underlying process or losing output from it?