Earlier quoted context omitted.
> It's one thing to say to "use code with caution" but it's another thing to pretend to run a calculation and then hallucinate the answer (or hallucinate that it's running code). Not to an LLM, it isn't. You're asking for "reasoning" features, the idea of having a model of what's needs to happen and whether or not the output matches the constriants of the model. And that's not what LLMs do, at all. That Bard attempts…
I think you're making some improper assumptions about my familiarity with the technology. The whole point of adding grounding via external plugins, code interpreters, or retrieval augmentation is to reduce hallucinations - if a block of code and results are going to be presented/represent itself as the execution output, then it better damn well be directly retrieved and not be rendered by the LLM itself if Google can…
An LLM is a regressive generator. It can only take the output of the execution as input and generate tokens based on it. You got the impressionist, under-water refracted version of the output.