LLMs are vectorial databases with losses that index statistically filled data, which uses a text interface to query such statistically filled data. The output is a string concatenation.

By the nature of the used architecture in such software, the used algorithms, when queried (prompted), you can get random mixed data as output, ERRORS, due to undesired indexes getting closer at one point while the string was being concatenated for the output, what affects the rest of the indexed content that will be concatenated.

And this is intrinsic to this tech. The larger the context, the greater the probability of get mixed data. And if the provider lowers the precision of those indexes -in order to decrease hardware and energy resources consumption- such probability increases to the point where those errors are granted.

Anyway, even knowing that the queries can return wrong/mixed data in the responses (errors), the companies developing this, decided to introduce a new product, that connects such LLMs responses to the command console, latter connected to internet, running commands from such returned responses witch obviously can contain whatever mixed random. Then we started to hear "oh, it deleted my directory", etc.

Again, One have such described statistical database with text interface, witch query the database recursively with the output text of the previous query, and this is connected to the command console. Larger contexts, several times... What should we expect as result? rhetoric question.

Implying sentience or consciousness is a convenient marketing strategy that has been introduced by anthropomorphising the names of all the methods and algorithms used. An "Agent" should be translated from such deceiving language to "context splitter querying in loop that consumes more tokens from us", or similar.

Wasn't the conventional wisdom to never feed raw input into `eval`?

Oops.

* > An "Agent" should be translated from such deceiving language to "context splitter querying in loop that consumes more tokens from us", or similar.

Please disregard this line. I wanted to point out that it increases the length of the context (and therefore the probability of errors) due the batch processing. But I redacted it incorrectly because I also wanted to imply that promoting the use such queries non-stop increases the billing through tokens consumption.