v1.0.1
CodeLeveler v1.0.1
English
A bug-fix release on top of 1.0.0. Installed 1.0.0 builds pick it up automatically, or run leveler update / /update.
Fixed
- Starting the TUI while an older local runtime is still busy no longer fails after 10 seconds: the client waits for the old runtime to finish and hands over to the new one
- A handover no longer hangs when another client has already started the replacement runtime
- A development build is recognised by the runtime it started, so it no longer restarts an identical runtime on every launch
- An idle background runtime shuts itself down once no client is attached and no work is running
- Every visible tool row in the TUI names what ran
- A message typed while a turn runs is sent automatically as the next turn once the runtime is ready, in order and only into the session it was written for; waiting no longer shows as "status unknown"
- Option lists in questions, pickers and approvals are numbered, and labels stay aligned when moving the cursor or past 9 → 10
Known limits
- Prebuilt binaries are not Apple- or Microsoft-signed. macOS or Windows may block the first run until you allow it
- Windows cannot deny network access per command. A command that requires that isolation is refused rather than run with the network open
- Windows has no local daemon socket. Sessions and
resumestill work - A confined Windows
!commandprints its output when it finishes, not while it runs
Install and usage: README.
Updates: README § Updates.
How the system is layered: Architecture.
中文
1.0.0 之上的修复版。已安装的 1.0.0 会自动更新,也可以用 leveler update 或 /update。
修复
- 旧的本地 runtime 还在忙时启动 TUI,不再等 10 秒后失败:客户端会等旧 runtime 做完,再交接给新的
- 另一个客户端已经拉起替代 runtime 时,交接不再卡住
- 开发构建能认出自己启动的 runtime,不会每次启动都重启一个相同的 runtime
- 没有客户端连接、也没有任务在跑时,空闲的后台 runtime 会自行退出
- TUI 里每一行可见的工具记录都写明执行了什么
- 任务运行中输入的消息,会在 runtime 就绪后按顺序自动作为下一轮发送,且只发往写它时所在的会话;排队等待不再显示为"状态未知"
- 提问、选择器和批准里的选项带编号,移动光标或从 9 到 10 时标签不再错位
已知限制
- 预编译包没有苹果或微软的官方签名。macOS 或 Windows 第一次运行时可能会拦截,需要你允许一次
- Windows 还不能按命令断开网络。需要断网隔离的命令会被拒绝,而不会在网络仍开放时继续跑
- Windows 没有本地 daemon 套接字。会话和
resume仍然可用 - Windows 上受隔离的
!command结束后才打印输出,不会边跑边刷
安装与使用见 README。
更新见 README · 更新。
系统怎么分层见 架构说明。