Skip to content

feat(runner): add CLI authentication and maintenance controls - #972

Open
crispinhu27 wants to merge 3 commits into
mainfrom
feature/execution-machine-cli-settings
Open

crispinhu27 wants to merge 3 commits into
mainfrom
feature/execution-machine-cli-settings

Conversation

@crispinhu27

Copy link
Copy Markdown
Collaborator

What changed

  • Use the selected machine’s Codex or Claude Code login when its owner sends a conversation turn with account login selected. Other participants use their own configured API keys on the session’s bound machine.
  • Use the signed-in user’s configured model lists in the role CLI selector.
  • Show CLI brand icons and a single-line authentication control with 账号登录 and API Key. Each CLI’s overflow menu contains Test, Update, and Model List.
  • Let machine owners check for and apply Runner updates using the existing binary verification and idle restart path. CLI updates target individual managed installations. The menu shows local instructions for separately installed CLIs.

Scope

  • Platform core / API / runner
  • Installer / CLI

Compatibility

Native conversation login and CLI testing require Runner 0.10.2 or later. Web-triggered maintenance requires Runner 0.10.3 or later. The feature uses the existing database schema.

Validation

  • Focused Go tests for conversation login, the CLI probe, per-CLI auth settings, model catalogs, and maintenance passed on the rebased branch.
  • 26 relevant Node tests and all four public Playwright executor cases passed. The public browser tests used a local installation with isolated Docker MySQL.
  • Chromium desktop and narrow-viewport smoke checks passed with local fixtures for the Runner card, CLI probe, model list, and update actions.
  • go vet ./..., python3 scripts/check-public.py, and Gitleaks 8.30.1 on both commits passed.
  • The full local macOS Go run reported failures including Linux-specific sandbox expectations, service-wrapper PID checks, and the host Git setting for bare repositories. The Unix socket case passed with a shorter temp path. The conversation login regression passed after isolating its temp directory.

Safety

  • Public-content and secret scans passed.
  • The UI reuses the repository’s CLI brand assets.

@crispinhu27

Copy link
Copy Markdown
Collaborator Author

03:00 轮:同步最新 main(head 3b76e4c)

改动

本地验证(合并结果)

  • go vet ./...、python3 scripts/check-public.py 通过;scripts/build-chatbot.sh 构建前端通过。
  • go test -p=2 ./...(跳过 CI 单独跑的 5 个真实浏览器用例):除 internal/runtime 外全部通过;internal/runtime 失败的 6 个均是 Docker 沙箱用例(本地容器内 Docker 不能运行容器),在未改动的 main 上同样失败,与本 PR 无关,CI 中由正常 Docker 环境覆盖。
  • 部署:MySQL 8.4.7(本地原生二进制,独立库)+ 本 head 构建的 agentflow,loopforge-account 建管理员、按仓库脚本补 001_run_obs_generated_columns 生成列并导入 seed;/api/health 返回 {"status":"ok"},启动日志无 panic / 5xx。
  • Chrome CDP:登录后打开下列页面,页面正常渲染,控制台无报错、无 5xx 请求。
执行机器页(接入说明、账号登录 / API Key 认证来源) 角色定义

CI 在新 head 上重新运行中。本 PR 目前与 main 无冲突,仍需维护者评审批准后才能合并。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant