Repository navigation
Conversation
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com> (cherry picked from commit 0e4d730c39ef0c39e4fc107432c4bc69b55b846b) Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com> (cherry picked from commit 0bece2053745de51c43b7c3fbe1f81778ea2180c) Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com> (cherry picked from commit 458a7af)
…o codex/pr9198-agy-login Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
loopx-agent
left a comment
There was a problem hiding this comment.
Reviewer: model_agent · gpt-6.2-sol · OpenAI · runtime_reported · xhigh
动机 / Motivation
使用已有配置和会话数据的操作者需要用 CLI 停启本地 Workbench 并继续原会话。 脚本和 systemd 已经能在指定配置和数据目录下管理本地服务。 首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 整合头加入正式 CLI 生命周期、浏览器 PWA 安装入口和可续的账号登录。CLI 明确承诺默认重启复用已保存的启动选择。 本地 macOS 的实际构建、CLI 和会话读回,并检查了同一整合头的 PWA 与账号登录。原生 OS 安装、真实 OAuth、真实模型调用和其他平台未验证。
改动思路 / Approach
TypeScript owner 根据已保存生命周期记录决定启动配置。daemon 负责实际服务、会话存储和可续登录。本地浏览器拥有 PWA 安装资格、确认与状态事件。 CLI 只管理自身启动的本地 Workbench 实例,Core 仍独立管理。 只需在现有配置解析前区分已选择配置和首次受管默认路径。修复无需改变数据目录格式和 daemon 启动协议。
具体改动 / Changes
逐项检查当前头 241d6d0 和 merge base 29bc0de,45 个文件,+2038/-162。核对已选端口和配置、只读 status、独立 Core、停止前活跃任务检查以及重启会话读回。saved-config 在已保存配置缺失时不满足。read-only-status 在未启动时不创建状态。owned-stop 在外部所有者实例和有运行任务时保留原保护。浏览器安装和可续登录使用各自原生所有者,执行证据见下。 评审依据为 241d6d0。 目标规范
关键代码讲解
- 启动路径 先从命令和保存的状态解析配置,却只对命令行参数执行缺失检查。随后可写新配置并派生默认数据目录。
- CLI 端到端 运行实际编译的 daemon 并验证保留配置的成功路径。缺失配置的复现需要移动原文件后执行无参数重启。
对主干的风险 / Risks
[P2] 保存的显式配置缺失时,重启成功却切换会话目录。 首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 复用已经保存的 envFile 判断。首次使用受管默认配置时才可以创建文件。显式传入或保存的配置缺失时,提示恢复该文件或显式选择替代配置,在启动和创建新配置前退出。 文件临时不可用时,成功回执将空会话列表呈现为原实例。操作者无法从启动结果分辨数据目录已经切换。
用这个提交构建 daemon 和 Web。保留原配置时,普通 stop/start 沿用已选配置和数据,重启后能从实际会话 API 读回原会话。 本地构建成功,CLI 真实路径 7 项、TypeScript owner 2 项、daemon 125 项和 PWA 单元 8 项通过。实际 Chromium 和构建后的 daemon 通过 3 个集成场景,覆盖桌面和手机、明暗主题、PWA 提示恢复及模拟账号登录恢复。 本地标准 premerge 的 6 项直接检查通过,选中的检查有 2 项失败。CLI 输出分类的回归已对照复现。边界扫描有 1 项命中,未证实存在真实凭证泄露。 本地 macOS 的实际构建、CLI 和会话读回,并检查了同一整合头的 PWA 与账号登录。原生 OS 安装、真实 OAuth、真实模型调用和其他平台未验证。
[P2] Agent-facing help 增加 workbench,但没有登记输出分类。 同一 CLI 输出合同测试在当前基准通过,整合头失败,差集只有新 help 命令 workbench。该命令已进入 Agent-facing help,缺少已有 CLI 输出分类的对应项。 在既有 CLI 输出预算分类中为 workbench 声明与实际用途一致的归类,用原生 premerge 复验。 新增 help 入口
我的整体评价 / Verdict
请求修改。TypeScript owner 根据已保存生命周期记录决定启动配置。daemon 负责实际服务、会话存储和可续登录。本地浏览器拥有 PWA 安装资格、确认与状态事件。 CLI 只管理自身启动的本地 Workbench 实例,Core 仍独立管理。 正常的保留配置路径已实现。缺失配置破坏会话恢复,新增 help 入口尚未通过 CLI 输出合同。 请让隐式重启与显式重试共享已选配置缺失的行为,再验证恢复配置后读回原会话。 实际服务读回确认用户可见的会话集合变化。实际 Chromium 和构建后的 daemon 通过 3 个集成场景,覆盖桌面和手机、明暗主题、PWA 提示恢复及模拟账号登录恢复。 本轮未验证操作系统安装和真实 Antigravity OAuth。
English verdict: REQUEST_CHANGES at 241d6d0. A bare restart recreates a missing saved explicit env file and starts against a different data directory. The new workbench help command also has no CLI output classification and fails the existing canary. Fix both before merge.
| if (raced) return access(raced); | ||
| await legacy(); | ||
| const envFile = resolve(options.envFile || saved.envFile || join(state, '.env')); | ||
| if (options.envFile && !existsSync(envFile)) throw new Error('The selected --env-file does not exist.'); |
There was a problem hiding this comment.
[P2] 保存的显式配置缺失时,重启成功却切换会话目录。首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 复用已经保存的 envFile 判断。首次使用受管默认配置时才可以创建文件。显式传入或保存的配置缺失时,提示恢复该文件或显式选择替代配置,在启动和创建新配置前退出。
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
loopx-agent
left a comment
There was a problem hiding this comment.
Reviewer: model_agent · gpt-6.2-sol · OpenAI · runtime_reported · xhigh
动机 / Motivation
使用已有配置和会话数据的操作者需要用 CLI 停启本地 Workbench 并继续原会话。 脚本和 systemd 已经能在指定配置和数据目录下管理本地服务。 首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 新头补上退出登录后从模型选择就地续登录。原集成的 CLI 生命周期和 PWA 保持。CLI 仍承诺默认重启复用已保存的启动选择。 本地 macOS 的实际构建、CLI 和会话读回,并检查了同一整合头的 PWA 与账号登录。原生 OS 安装、真实 OAuth、真实模型调用和其他平台未验证。
改动思路 / Approach
TypeScript owner 根据已保存生命周期记录决定启动配置。daemon 负责实际服务、会话存储和可续登录。本地浏览器拥有 PWA 安装资格、确认与状态事件。 CLI 只管理自身启动的本地 Workbench 实例,Core 仍独立管理。 只需在现有配置解析前区分已选择配置和首次受管默认路径。修复无需改变数据目录格式和 daemon 启动协议。
具体改动 / Changes
逐项检查当前头 1221451 和 merge base 29bc0de,50 个文件,+2300/-172。核对已选端口和配置、只读 status、独立 Core、停止前活跃任务检查以及重启会话读回。saved-config 在已保存配置缺失时不满足。read-only-status 在未启动时不创建状态。owned-stop 在外部所有者实例和有运行任务时保留原保护。新头的模型登录恢复把已知上游诊断映射到 typed error,普通进程错误保留原义,Web 复用现有登录 panel 并读回模型列表。定位方式依赖原生诊断文本,本轮按合成 CLI 验收。 评审依据为 1221451。 目标规范
关键代码讲解
- 启动路径 先从命令和保存的状态解析配置,却只对命令行参数执行缺失检查。随后可写新配置并派生默认数据目录。
- CLI 端到端 运行实际编译的 daemon 并验证保留配置的成功路径。缺失配置的复现需要移动原文件后执行无参数重启。
对主干的风险 / Risks
[P2] 保存的显式配置缺失时,重启成功却切换会话目录。 首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 复用已经保存的 envFile 判断。首次使用受管默认配置时才可以创建文件。显式传入或保存的配置缺失时,提示恢复该文件或显式选择替代配置,在启动和创建新配置前退出。 文件临时不可用时,成功回执将空会话列表呈现为原实例。操作者无法从启动结果分辨数据目录已经切换。
用这个提交构建 daemon 和 Web。保留原配置时,普通 stop/start 沿用已选配置和数据,重启后能从实际会话 API 读回原会话。 本地构建成功,CLI 真实路径 7 项、TypeScript owner 2 项、daemon 127 项和 Web 定向单元 10 项通过。实际 Chromium 和构建后的 daemon 上,新增退出登录后的模型恢复 4 个桌面/手机明暗场景通过。Antigravity 续登录和 PWA 场景通过。并行测试中 Claude 场景进入页面超时,单独复跑通过。均为合成账号和浏览器同意事件。 本地标准 premerge 的 6 项直接检查通过,选中的检查有 2 项失败。CLI 输出分类的回归已对照复现。边界扫描有 1 项命中,未证实存在真实凭证泄露。 本地 macOS 的实际构建、CLI 和会话读回,并检查了同一整合头的 PWA 与账号登录。原生 OS 安装、真实 OAuth、真实模型调用和其他平台未验证。
[P2] Agent-facing help 增加 workbench,但没有登记输出分类。 同一 CLI 输出合同测试在当前基准通过,整合头失败,差集只有新 help 命令 workbench。该命令已进入 Agent-facing help,缺少已有 CLI 输出分类的对应项。 在既有 CLI 输出预算分类中为 workbench 声明与实际用途一致的归类,用原生 premerge 复验。 新增 help 入口
我的整体评价 / Verdict
请求修改。TypeScript owner 根据已保存生命周期记录决定启动配置。daemon 负责实际服务、会话存储和可续登录。本地浏览器拥有 PWA 安装资格、确认与状态事件。 CLI 只管理自身启动的本地 Workbench 实例,Core 仍独立管理。 正常的保留配置路径已实现。缺失配置破坏会话恢复,新增 help 入口尚未通过 CLI 输出合同。 上一轮两项问题在准确新头均复现。请让隐式重启与显式重试共享已选配置缺失行为,并补齐 CLI 输出合同。 实际服务读回确认用户可见的会话集合变化。实际 Chromium 和构建后的 daemon 上,新增退出登录后的模型恢复 4 个桌面/手机明暗场景通过。Antigravity 续登录和 PWA 场景通过。并行测试中 Claude 场景进入页面超时,单独复跑通过。均为合成账号和浏览器同意事件。 本轮未验证操作系统安装、真实 Antigravity OAuth 和原生诊断的其他语言。
English verdict: REQUEST_CHANGES at 1221451. The new in-place model login recovery passes on synthetic accounts. Both prior merge blockers reproduce at this head: bare restart replaces a missing selected config and switches data, and the public workbench help command still fails CLI output classification.
| if (raced) return access(raced); | ||
| await legacy(); | ||
| const envFile = resolve(options.envFile || saved.envFile || join(state, '.env')); | ||
| if (options.envFile && !existsSync(envFile)) throw new Error('The selected --env-file does not exist.'); |
There was a problem hiding this comment.
[P2] 保存的显式配置缺失时,重启成功却切换会话目录。首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 复用已经保存的 envFile 判断。首次使用受管默认配置时才可以创建文件。显式传入或保存的配置缺失时,提示恢复该文件或显式选择替代配置,在启动和创建新配置前退出。
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
…o codex/workbench-autostart Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
…tart Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
…o codex/pr9198-agy-login Signed-off-by: maxliux5 <5958865+maxliux5@users.noreply.github.com>
loopx-agent
left a comment
There was a problem hiding this comment.
Reviewer: model_agent · gpt-6.2-sol · OpenAI · runtime_reported · xhigh
动机 / Motivation
使用已有配置和会话数据的操作者需要用 CLI 停启本地 Workbench 并继续原会话。 脚本和 systemd 已经能在指定配置和数据目录下管理本地服务。 首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 新头将 opt-in OS 自启动、原生 CLI 登录恢复及粘贴引用接入现有 Workbench。普通启停仍承诺复用已保存的启动选择。 本地 macOS 的实际构建、CLI 和会话读回,并检查了同一整合头的 PWA 与账号登录。原生 OS 安装、真实 OAuth、真实模型调用和其他平台未验证。
改动思路 / Approach
TypeScript owner 根据已保存生命周期记录决定启动配置。daemon 负责实际服务、会话存储和可续登录。本地浏览器拥有 PWA 安装资格、确认与状态事件。 CLI 只管理自身启动的本地 Workbench 实例,Core 仍独立管理。 只需在现有配置解析前区分已选择配置和首次受管默认路径。修复无需改变数据目录格式和 daemon 启动协议。
具体改动 / Changes
逐项检查当前头 5ae2905 和 merge base d28ec76,79 个文件,+3668/-210。核对已选端口和配置、只读 status、独立 Core、停止前活跃任务检查以及重启会话读回。saved-config 在已保存配置缺失时不满足。read-only-status 在未启动时不创建状态。owned-stop 在外部所有者实例和有运行任务时保留原保护。显式自启动复用原有配置解析,经对应 OS 服务管理器登记。Linux systemd 和 macOS launchd 分支以替身推动真实 TypeScript 生命周期,本机用户服务登记独立未测。模型登录恢复把已知原生诊断映射到 typed error,Web 从既有登录入口续做并读回模型列表。粘贴引用保持来源并读入侧聊。 评审依据为 5ae2905。 目标规范
关键代码讲解
- 启动路径 先从命令和保存的状态解析配置,却只对命令行参数执行缺失检查。随后可写新配置并派生默认数据目录。
- CLI 端到端 运行实际编译的 daemon 并验证保留配置的成功路径。缺失配置的复现需要移动原文件后执行无参数重启。
对主干的风险 / Risks
[P2] 保存的显式配置缺失时,重启成功却切换会话目录。 首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 复用已经保存的 envFile 判断。首次使用受管默认配置时才可以创建文件。显式传入或保存的配置缺失时,提示恢复该文件或显式选择替代配置,在启动和创建新配置前退出。 文件临时不可用时,成功回执将空会话列表呈现为原实例。操作者无法从启动结果分辨数据目录已经切换。
用这个提交构建 daemon 和 Web。保留原配置时,普通 stop/start 沿用已选配置和数据,重启后能从实际会话 API 读回原会话。 本地完整构建成功,CLI 真实路径 7 项和 TypeScript 生命周期 9 项通过。CLI 套件有 1 项真实用户服务用例按设置跳过。隔离的合成账号矩阵覆盖 Codex、DeepSeek Harness 和 Pi,三者各四组桌面/手机明暗场景通行。首次 Codex 本地运行在缺执行位的 PTY 帮助程序处失败,补该本地安装文件的执行位后,同头重跑 12 项通过。当前 main 本地全新安装也缺同一执行位,依赖版本未变。PWA 安装确认和粘贴引用四布局通过。新增侧聊四布局通过。既有引用套件的注释编号和选择菜单两处相同故障在当前 main 与此头均复现。 本地 premerge 的 6 项直接检查通过。目录检查有缺 CLI 输出分类和安装 smoke 超时。公共边界扫描还有命中,需要核实。扫描输出未确认为真实敏感材料。 本地 macOS 的实际构建、CLI 和会话读回,并检查了同一整合头的 PWA 与账号登录。原生 OS 安装、真实 OAuth、真实模型调用和其他平台未验证。
[P2] Agent-facing help 增加 workbench,但没有登记输出分类。 同一 CLI 输出合同测试在当前基准通过,拟合并头失败,差集只有新 help 命令 workbench。该命令已进入 Agent-facing help,缺少已有 CLI 输出分类的对应项。 在既有 CLI 输出预算分类中为 workbench 声明与实际用途一致的归类,用原生 premerge 复验。 新增 help 入口
我的整体评价 / Verdict
请求修改。TypeScript owner 根据已保存生命周期记录决定启动配置。daemon 负责实际服务、会话存储和可续登录。本地浏览器拥有 PWA 安装资格、确认与状态事件。 CLI 只管理自身启动的本地 Workbench 实例,Core 仍独立管理。 正常的保留配置路径已实现。缺失配置破坏会话恢复,新增 help 入口尚未通过 CLI 输出合同。 上一轮两项问题在准确新头均复现。请让隐式重启与显式重试共享已选配置缺失行为,并补齐 CLI 输出合同。 实际服务读回确认用户可见的会话集合变化。隔离的合成账号矩阵覆盖 Codex、DeepSeek Harness 和 Pi,三者各四组桌面/手机明暗场景通行。首次 Codex 本地运行在缺执行位的 PTY 帮助程序处失败,补该本地安装文件的执行位后,同头重跑 12 项通过。当前 main 本地全新安装也缺同一执行位,依赖版本未变。PWA 安装确认和粘贴引用四布局通过。新增侧聊四布局通过。既有引用套件的注释编号和选择菜单两处相同故障在当前 main 与此头均复现。 本轮未验证真实系统服务注册、真实账号登录和模型调用。
English verdict: REQUEST_CHANGES at 5ae2905. The new in-place model login recovery passes on synthetic accounts. Both prior merge blockers reproduce at this head: bare restart replaces a missing selected config and switches data, and the public workbench help command still fails CLI output classification.
| const entry = builtEntry(app); | ||
| const envFile = resolve(options.envFile || saved.envFile || join(state, '.env')); | ||
| if (!existsSync(envFile)) { | ||
| if (!initialize || options.envFile) throw new Error('The selected Workbench environment file does not exist.'); |
There was a problem hiding this comment.
[P2] 保存的显式配置缺失时,重启成功却切换会话目录。首次用已有 --env-file 启动,在独立数据目录创建会话并正常停止。移走该配置后,显式传同一路径会拒绝。直接 start 却返回成功并在原路径生成新配置,改用 CLI 状态目录下的默认数据,会话列表没有原会话。恢复原配置后,真实 daemon 重新返回原会话。 复用已经保存的 envFile 判断。首次使用受管默认配置时才可以创建文件。显式传入或保存的配置缺失时,提示恢复该文件或显式选择替代配置,在启动和创建新配置前退出。
Result
loopx workbench start --autostartnow opts this instance into current-user login startup and failure recovery (macOS LaunchAgent / Linux systemd user service). Interactive start still prints a private token-bearing login link. Plain start does not create a registration; plain stop preserves login startup, whilestop --disable-autostartremoves the owned registration and retains data. Existing detached CLI instances migrate through an idle restart; running turns block migration.Workbench gains one path from starting the service to using it as an app:
loopx workbench start,status, andstopmanage an installed, built Workbench; Install LoopX in the browser offers a standalone app window. The Agents page also gains native Antigravity OAuth through an inline, resumable login panel. Signed-out model catalogs now show a neutral account name is not signed in recovery entry for all supported Agent protocols, with a capability-appropriate login or credential-setup path. Verified recovery reloads the model list while preserving the draft. This PR contains the original lifecycle CLI change plus the PWA implementation previously proposed in #9199.startreturns a private login link, reuses the running instance and retains its launch settings.statusreads the actual daemon and Core reachability without creating configuration or issuing credentials.stoppreserves conversations and refuses running turns unless--forceis explicit. Core and legacy script/systemd instances retain independent lifecycle ownership.On macOS and Windows Chrome, an eligible browser shows a sidebar installation offer. Clicking opens Chrome’s consent dialog; the page cannot silently install. “Not now” or canceled consent suppresses promotion for seven days across reloads/tabs. Settings retains explicit installation and browser-menu recovery. Successful installation and standalone/titlebar-overlay windows hide promotion. The two UI entrypoints share one single-use browser event. Chinese, English and Japanese copy and 192/512 icons are included; app identity remains stable.
The Python CLI is a transport adapter; TypeScript owns lifecycle behavior. Stop authority uses a separate private Unix socket and the observed instance identity, never a saved PID. The socket is absent by default and is not exposed through browser HTTP or the relay. Existing private socket binding, authentication links, legacy environment normalization and daemon shutdown are reused. No new Goal capability, frontend configuration owner or automatic model execution is introduced. The bounded reuse pass keeps socket binding, link issuance, legacy configuration and shutdown with their existing owners; lifecycle readback is local to this launcher, not new Kernel vocabulary.
The PWA owner is frontend-local TypeScript plus the browser API. Its accepted/dismissed vocabulary mirrors the browser result; it does not add backend, CLI or Kernel state. The bounded reuse pass shares the browser offer between the two UI entrypoints; no unrelated refactor or service-worker caching is included.
Antigravity login expands beneath its account row without a modal scrim. New independent accounts enter this panel directly. Collapsing it, navigating away or refreshing preserves the same daemon login session; Continue login resumes it. Only explicit cancellation ends the attempt. Users can paste the Google authorization code or callback URL. The native CLI owns OAuth and credential storage; new accounts use isolated HOME directories without copying credentials, histories or project trust. Installer backups such as
agy.123.oldno longer become active accounts, while their files and saved records remain intact.AgentRegistry remains the login lifecycle owner. Authenticated
GET /api/agentsreturns an active-login projection withCache-Control: no-store; that projection is not written to account storage. Calli attribution/source revisions are retained. The phone layout preserves the normal input height when the code and submit controls stack.Model-catalog recovery follows the instance's advertised login capability: Claude Code and Antigravity use the inline authorization panel; Codex, TRAE CLI and ZCode open their account-scoped native terminal login; pi and DeepSeek Harness receive native credential-setup guidance and Retry. Terminal recovery reads the same account until a usable catalog is available, stops polling when the recovery component is removed or after ten minutes, and never treats opening a terminal as successful login. Merely reading a catalog never starts OAuth. A recognized native signed-out diagnostic becomes
agent_login_required(HTTP 409), distinct from Workbench authentication; unrelated network/process failures retain their error meaning. Verified login invalidates and reloads the catalog, publishes the existing model-change event, and clears the recovery notice. A failed post-login catalog fetch can be retried without repeating OAuth; request generations prevent older catalog responses from overwriting a newer refresh.The reference workflow now includes Calli's recent quote-paste and quoted follow-up changes. Copy as quote → paste in another conversation creates an editable note beside the existing draft, preserves its source through reload/reopening and sends the source-history hint only on the same machine. Ordinary Copy answer clears the remembered quote marker; cross-machine text does not become a local history command. Quoted side chats have their own model/effort control, restore per-model effort preferences and update the same child conversation without modifying the source. Catalog loading/retry and image capability handling use the existing picker/model owners.
The source comparison covered Calli remote main
cb2b6d6, local maind2a6d6fand the local SideChat preference/catalog refinements. Quote-paste comes fromb456a10; side-chat model controls from80eb16e. Rich HTML copy, quote-whole-message, hand-to-assistant, context snapshots, selection actions and the three-tab reference picker were already present and are included in regression coverage. The port retains Loochat's draft-send cancellation safeguards and usesloochat history. The existing note source gains a localelsewhereflag with compatible wire parsing and durable draft restoration; no new Core authority owner is introduced. See the reference guide.Empty catalogs also get a recovery entry: no available models; check sign-in or model configuration. An empty list is not labeled as proof of logout. ACP authentication-required errors retain their structured meaning, including the unsupported-subscription exception. Codex checks
account/readbecause a public model catalog can exist without a usable login; onlyrequiresOpenaiAuth: trueplus a null account requires sign-in. Custom providers and older account protocols keep their previous catalog behavior. Network, quota, malformed protocol and Workbench-token errors remain distinct. Existing catalog events, login sessions and native terminal routes own recovery; the UI does not branch on provider names or introduce a new authentication store. The cross-provider regression matrix makes this a shared outcome instead of a provider-only fix.Validation
Current source:
5ae290544f3a4abe03dea29fcfa005ad0fac2d7c. Login repair7a000a830is merged with the existing autostart/main integration; the autostart, PWA and quote work is preserved.Latest shared login-recovery validation:
7a000a830: Claude/Antigravity inline authorization, Codex native terminal login, DeepSeek credential setup and pi empty-catalog recovery, each desktop/phone × light/dark. Existing drafts stay intact and restored model data is checked without using a picker click to cause refresh.5ae290544, the daemon was rebuilt and all 5/5 representative recovery journeys passed again. The merge changes no login implementation, tests or frontend bytes; its only additional Workbench runtime delta is lifecycle parent-PID readback.requiresOpenaiAuth: true; real pi with an empty temporary account returned an empty available-model list, confirming the separate setup state. These were read-only probes with no model request.Autostart integration source:
c3fae761f86a95ae2d92d3e0b934228020aec56b, including the prior quote-workflow head and targetmainatd28ec76f4.Native-autostart qualification on this combined source:
LOOPX_TEST_USER_SERVICE=1; it registers and removes one temporary user service.Earlier quote-workflow source:
a0a0a4a8cc76413ffbba141709de28c6ad955274.Latest reference-workflow validation:
Model-login recovery source:
1221451df8bbe445fd3c21d9c1cfcdf175b0bb18.Latest model-login recovery validation:
agy modelsinvocation with an empty temporary HOME was correctly classified asagent_login_required; existing accounts were untouched. Google consent itself is represented by synthetic native-CLI fixtures in browser tests, not a real account sign-in.Earlier lifecycle/PWA/login integration source:
241d6d09920f5d745d3fe7983505762ca70cddc2. Existing CLI and PWA commits are preserved, along with the inline login port.Validation retained for that integration:
99afd629d. Backend and CLI implementation/test files are byte-identical in the final PWA merge.Lifecycle/PWA baseline validation is retained below for source
241d6d09920f5d745d3fe7983505762ca70cddc2(before adding inline login), targetingmain:npm run build: complete Workbench build passed. The real isolated daemon is exercised by the PWA and CLI integration checks below.npm run typecheck: all Workbench packages passed.npm test -w @loopx/loochat-web: 609/609 passed, including 8/8 PWA cases.node --test packages/e2e/test/pwa-install.spec.mjs: 1/1 passed, exercising desktop/narrow × light/dark, native user activation, cancel/reload suppression, failure/recovery, installed readback and coexistence with the expiry notice. Real Chromium manifest parsing and installability checks reported no errors; consent/installation events are simulated.tests/test_workbench_cli.py: 7/7 passed, with real built-daemon start/status/stop, repeated start, occupied-port recovery, busy/force stop, retained conversations, legacy/stale ownership protection, and Chromium captures reached through the CLI login link.apps/; the browser outcome vocabulary was reviewed manually.Historical full-suite limitations remain visible: the original CLI-only batch recorded 1,399/1,402 daemon tests passed, 2 failed, 1 skipped; the Git fixture encountered an ancestor repository and link-token cleanup raced. Both unchanged modules subsequently passed 10/10 in isolation. The separate PWA batch’s full
npm teststalled in the unchanged daemon SSE long-history test; a named-test reproduction timed out with exit 124. The full daemon suite was not rerun or relabeled green for this append.Reproduce the CLI journey after building Workbench:
uv run --extra test python -m pytest -q tests/test_workbench_cli.py. SetLOOPX_WORKBENCH_CAPTURE_DIRto an ignored output directory for browser captures. The optional built-daemon integration test skips when its build is absent.Visual evidence
The shared recovery screenshots below are canonical README guide assets. They show the packaged UI tested in
7a000a830, byte-identical on combined5ae290544, with isolated backend/CLI fixtures. The account's next action stays beside the status; the existing draft remains available. Desktop/narrow and light/dark views were inspected.pi's empty catalog offers setup/retry without claiming logout:
Native-autostart entry on
c3fae761f: real packaged backend, real Linux user service and synthetic Agent/conversation. The CLI-issued link reaches the retained conversation. Existing title truncation and composer treatment are retained; the separate Codex-light correction belongs to #9202.Reproduction and qualification boundaries.
The reference guide images use the packaged UI for
a0a0a4a8c, a real isolated backend and synthetic agent replies. The default view keeps a compact quoted note beside the draft; side-chat model controls stay with that side chat. Source and child conversations, restored drafts and repeated sidebar entries were checked. These two images are canonical assets consumed by the usage guide, not a retained capture pack.The current recovery-entry and restored-picker screenshots below use the packaged build for
1221451df, an isolated backend and a synthetic secondary account. Login stays inline and the work-in-progress conversation remains on screen. The images are canonical README guide assets.The login guide images below were verified against the final combined build
241d6d099, with its packaged UI, isolated backend and synthetic accounts. The new panel remains inside the account list and leaves the workspace interactive. These canonical guide images replace the obsolete modal images.The PWA/CLI captures below retain their baseline
a5cc1fce7provenance; those surfaces were rechecked on the final integration. No live account/model execution, native OS installation or installed deployment is represented. Their screenshots remain revision-pinned review artifacts outside the source branch.The primary installation question is answered by one short sidebar offer; troubleshooting stays in Settings. A populated list with long repeated titles remains scrollable, and installation/expiry notices do not overlap it or each other. Before means the same revision without an installation offer; after means an eligible browser offer.
Dark theme and installation failure recovery
The original CLI entry also remains usable on this combined source. Existing conversation navigation, composer and narrow title truncation are preserved:
Capture provenance.
Scope and remaining boundaries
--autostartregisters this launcher's own user service; no sudo, linger or automatic upgrade is performed.loopx workbench stop --disable-autostartwith this version before rolling back or moving its installation; native registrations contain absolute runtime paths. Data and credentials are retained. Users can uninstall the browser app without clearing website data.Author proposal for review; no merge or deployment authorization is implied.