Like with many things, it depends entirely on how you define "real terminal"; that is, what a "real terminal" must do before it satisfies your definition. If it's "takes input and deterministically executes its instructions, producing output along with side effects," a well-trained model with argmax sampling could well meet the bar. if given the appropriate external interfaces.
generally i expect if i invoke `touch file` to see my file update date as now, on the filesystem. so i want to have a mapping between physical world (in this case, memory on my machine) and intelligence representation. If the LLM terminal, upon invoking `touch file` does not update the physical file, it is not a real terminal. you can argue that i will use the terminal itself to invoke `ls -la` and check the updated file, but verifying from an external scope is mandatory imho otherwise it's obvious you cannot logically demonstrate that. hope i was clear
