Is there any file in VM which is automatically read by LLM before session start? You mentioned some internal folder which contains files that detail how network requests from the API are handled. So are these instructions for LLM to read before reach session? Can you override these instructions, so LLM will have already custom conversation context prior reach session? That would work as sort of long term memory, LLM could drop summary of the whole session before end, so next time you start session on same VM LLM will be already familiar.
Or, if this VM will be allocated to another user without full reset—then it could be surprise for another user.
Great idea! The web requests file doesn’t seem to be read by the LLM during boot-up (and neither does any other file on the system), instead it’s a process run on the Linux machine which wraps around the python processes the LLM has access to. The LLM can only interact with the VM through this web request handler. It’s read-only so can’t be modified so that they’re handled differently when you boot up another chat session on the same VM. Regarding your last point, I haven’t noticed any files surviving a VM reset so far.
Is there any file in VM which is automatically read by LLM before session start? You mentioned some internal folder which contains files that detail how network requests from the API are handled. So are these instructions for LLM to read before reach session? Can you override these instructions, so LLM will have already custom conversation context prior reach session? That would work as sort of long term memory, LLM could drop summary of the whole session before end, so next time you start session on same VM LLM will be already familiar. Or, if this VM will be allocated to another user without full reset—then it could be surprise for another user.
Great idea! The web requests file doesn’t seem to be read by the LLM during boot-up (and neither does any other file on the system), instead it’s a process run on the Linux machine which wraps around the python processes the LLM has access to. The LLM can only interact with the VM through this web request handler. It’s read-only so can’t be modified so that they’re handled differently when you boot up another chat session on the same VM. Regarding your last point, I haven’t noticed any files surviving a VM reset so far.