Skip to content

OriginRouter CLI v0.4.7

Choose a tag to compare

@chengaoyan chengaoyan released this 28 Sep 03:43
· 23 commits to main since this release

OriginRouter CLI v0.4.7

English

This patch fixes CLI startup and runtime errors affecting Workspace, daemon, device removal, and local API flows.

  • Fix logout with device removal by signing the request with the current account epoch. Keep the installation's device identity key after sign-out.
  • Record the resolved provider and model in Agent session telemetry. Preserve the original error when a session fails before provider resolution.
  • Read the existing device identity in originrouter env print without entering the login-specific setup flow.
  • Restore Workspace's active-run spinner and fix a missing provider reference in the daemon.
  • Return consistent remote-share status from the dedicated and local status endpoints. Route model verification through the configured probe function.

Validation: 12 focused tests passed across Workspace, CLI login, local API, and session management. git diff --check passed. The full test suite and Windows verification were not run for this patch.

After publishing @originrouter/cli@0.4.7 to npm, existing users can check and install the update with:

originrouter update check
originrouter update install

Interactive startup also checks for updates. The default mode prompts the user after a newer npm version is cached; users who selected automatic updates install it when the CLI next starts and the system is idle.

中文

本次修复 Workspace、daemon、设备移除及本地 API 流程中的 CLI 启动和运行错误。

  • 退出登录并移除设备时,使用当前账户 epoch 签名移除请求;退出后保留本机安装的设备身份密钥。
  • Agent 会话遥测记录实际解析出的 Provider 和模型;如果会话在 Provider 解析前失败,保留原始错误。
  • originrouter env print 读取现有设备身份,不再进入登录专用的设备设置流程。
  • 恢复 Workspace 运行中的进度动画,并修复 daemon 中缺失的 Provider 引用。
  • 远程共享独立状态接口与本地状态摘要返回一致的数据;模型验证使用已配置的探测函数。

验证:Workspace、CLI 登录、本地 API 和会话管理的 12 项针对性测试通过;git diff --check 通过。本次未运行完整测试套件,也未进行 Windows 真机验证。

将 @originrouter/cli@0.4.7 发布到 npm 后,已安装用户可以执行:

originrouter update check
originrouter update install

交互式启动也会检查更新。默认模式会在缓存到新版 npm 包后提示用户;选择自动更新模式的用户会在下次启动且系统空闲时安装。