feat: surface task execution progress across Host Agent and Cloud
Host Agent now persists step-level execution detail locally (via a real TaskMetadataStore/Timeline wired into TaskRunner) and reports a bounded in-progress snapshot piggybacked on lease renewal. Cloud persists that snapshot per active assignment and exposes it through the existing task list/detail query path; Cloud Console renders it as a live badge. Host Agent's local console gains authenticated, read-only task list and detail/timeline pages (same-origin, server-rendered) with inlined screenshots. Also fixes a pre-existing gap in the shared Timeline: the actual per-step LLM prompt is now recorded instead of the task goal, benefiting both Runtime and Host Agent consoles. When a host uses the cloud planner transport, each decide call's prompt and resulting tool decision are durably logged in a new planner_decision_log table (with bounded retention) and browsable from Cloud Console; direct-transport hosts explicitly surface a "not reported" state. Includes Alembic migrations 0008 (progress columns on scheduled_tasks) and 0009 (planner_decision_log), bounded Host-Agent-local retention, dual-backend repository parity, and Vitest + pytest coverage. Task 6.5 (manual end-to-end device verification) remains. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Claude Opus 4.6
@@ -121,6 +121,39 @@ HOST_AGENT_CONSOLE_HISTORY_LIMIT=200
|
||||
- `HOST_AGENT_CONSOLE_HISTORY_LIMIT` — number of recent assignment/heartbeat
|
||||
entries the console retains before pruning older ones.
|
||||
|
||||
### Task progress storage and retention
|
||||
|
||||
The Host Agent persists step-by-step task execution state (metadata +
|
||||
timeline screenshots) to local SQLite/files on the edge machine. These
|
||||
paths are independent from the Runtime's own `tasks/tasks.sqlite3` and
|
||||
do not collide when both processes run on the same host.
|
||||
|
||||
```text
|
||||
HOST_AGENT_TASK_PROGRESS_DB_PATH=host_agent_data/task_progress.sqlite3
|
||||
HOST_AGENT_TASK_ARTIFACT_DIR=host_agent_data/history
|
||||
HOST_AGENT_TASK_RETENTION_MAX_COUNT=50
|
||||
HOST_AGENT_TASK_RETENTION_MAX_AGE_DAYS=7
|
||||
```
|
||||
|
||||
- `HOST_AGENT_TASK_PROGRESS_DB_PATH` — SQLite path for the Host Agent's
|
||||
task metadata store. Default: `host_agent_data/task_progress.sqlite3`.
|
||||
- `HOST_AGENT_TASK_ARTIFACT_DIR` — directory for timeline screenshots and
|
||||
step artifacts. Default: `host_agent_data/history`.
|
||||
- `HOST_AGENT_TASK_RETENTION_MAX_COUNT` — maximum number of completed
|
||||
tasks to retain. Default: `50`.
|
||||
- `HOST_AGENT_TASK_RETENTION_MAX_AGE_DAYS` — maximum age in days for
|
||||
retained tasks. Default: `7`. The more restrictive of count vs. age
|
||||
always wins.
|
||||
|
||||
**Viewing live and historical task progress:**
|
||||
|
||||
- **Host Agent console**: Open `http://127.0.0.1:8765/tasks` for the task
|
||||
list (status, device, timestamps). Click a task ID to see the detail page
|
||||
with full step-by-step timeline and inlined screenshots.
|
||||
- **Cloud console**: The Cloud Console task detail page shows the latest
|
||||
coarse-grained progress badge (step index, status, summary) that the Host
|
||||
Agent piggybacks on each lease renewal.
|
||||
|
||||
Treat `HOST_AGENT_CONSOLE_ALLOW_NON_LOOPBACK` as an explicit,
|
||||
operator-accepted risk: the console has no built-in TLS and no rate
|
||||
limiting, so a non-loopback bind exposes an unencrypted login form to
|
||||
|
||||
@@ -339,6 +339,12 @@ Console 默认连接 `http://127.0.0.1:8000`。已由上面启动脚本连接的
|
||||
`iphone-1` 会出现在设备列表中。不要在 Console 中重复登记同一台设备；当前登记
|
||||
操作只写入配置，不会自动 connect。
|
||||
|
||||
如果不想为 Console 单独起一个 `npm run dev` 进程，可以改为一次性构建后交给
|
||||
Runtime API 同源托管，见 `console/README.md` 的「Same-Origin, Single-Process
|
||||
Mode」一节：设置 `VITE_API_BASE_URL=` 构建，再用 `RUNTIME_CONSOLE_STATIC_DIR`
|
||||
指向构建产物启动 Runtime API，浏览器访问 `/ui/` 即可；改前端代码后需要重新
|
||||
`npm run build`，不支持热更新。
|
||||
|
||||
## 9. 启动云端受管 Host Agent
|
||||
|
||||
完成 Appium/WDA 真机验证后，可以把这台 Mac 作为只发起出站连接的边缘 Host。
|
||||
@@ -423,11 +429,28 @@ http://127.0.0.1:8765
|
||||
`DeviceManager` 上生效，无需重启 Host Agent。
|
||||
- 修改密码：更新本地操作账号密码，需要先输入当前密码。
|
||||
- 最近历史：近期 assignment 与 heartbeat 的执行记录。
|
||||
- **任务进度页面**：`http://127.0.0.1:8765/tasks` 展示本机 Host Agent 上已执行/正在执行
|
||||
的任务列表（状态、设备、时间戳），点击任务 ID 可查看逐步 timeline 含截图。
|
||||
|
||||
完整的 `HOST_AGENT_CONSOLE_*` 环境变量列表（端口、非回环 bind 的显式 opt-in、
|
||||
session TTL、历史记录条数上限等）参见 `docs/CLOUD_DEPLOYMENT.md`；生产/远程场景下
|
||||
应优先使用 SSH 端口转发访问该 Console，而不是直接把它暴露到非回环地址。
|
||||
|
||||
Host Agent 会把每步执行状态与截图持久化到本地 SQLite/文件系统，路径与 Runtime 自身的
|
||||
`tasks/tasks.sqlite3` 不冲突：
|
||||
|
||||
```bash
|
||||
# 任务进度持久化路径（默认值，可通过环境变量覆盖）
|
||||
# HOST_AGENT_TASK_PROGRESS_DB_PATH="host_agent_data/task_progress.sqlite3"
|
||||
# HOST_AGENT_TASK_ARTIFACT_DIR="host_agent_data/history"
|
||||
# HOST_AGENT_TASK_RETENTION_MAX_COUNT=50 # 最多保留 50 个任务
|
||||
# HOST_AGENT_TASK_RETENTION_MAX_AGE_DAYS=7 # 超过 7 天的任务自动清理
|
||||
```
|
||||
|
||||
Retention 策略取"数量上限与天数上限中更严格的"——即先按 `max_count` 取最近 N 个、
|
||||
再按 `max_age_days` 过滤掉过老的，最终保留两者中较小的集合。任务完成后，这些记录
|
||||
在 Console 的 `/tasks` 页面可查。
|
||||
|
||||
### 可选：由 Host Agent 托管 Appium 和 Runtime API
|
||||
|
||||
默认情况下 Host Agent **不会**自动启动 Appium 或本地 Runtime API：必须按
|
||||
|
||||
Reference in New Issue
Block a user