q792602257/agentic-mobile-control
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: surface task execution progress across Host Agent and Cloud

Browse Source 
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:
q792602257
2026-07-14 12:47:49 +08:00
co-authored by Claude Opus 4.6
parent c049c3c1b1
commit ec261d57c2
59 changed files with 3801 additions and 122 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/task-execution-progress-visibility/specs/host-agent-protocol/spec.md
+23
View File
@@ -0,0 +1,23 @@
## ADDED Requirements
### Requirement: Host Agent reports execution progress alongside lease renewal
The Host Agent SHALL optionally include a bounded, screenshot-free progress summary (current step index, step status, and a short plain-text summary) in its periodic lease-renewal request for an active assignment, and the control plane SHALL accept and store only the most recent such summary per active assignment.
#### Scenario: Progress is available at renewal time
- **WHEN** the Host Agent renews the lease for an in-progress assignment and has a current step index, status, and summary available
- **THEN** the renewal request includes that progress summary and the control plane overwrites any previously stored progress for that assignment with it
#### Scenario: Progress is not available at renewal time
- **WHEN** the Host Agent renews a lease without a progress summary available (e.g. before the first step completes)
- **THEN** the renewal request omits the progress field and any previously stored progress for that assignment is left unchanged
#### Scenario: Assignment reaches a terminal state
- **WHEN** an assignment's terminal result is recorded
- **THEN** the control plane's stored progress for that assignment is no longer treated as current and is not exposed as an in-progress status
### Requirement: Progress reports exclude screenshot and scene payloads
The control plane SHALL reject or ignore any progress field on a renewal request that includes screenshot, scene, or other bulk payload data beyond the bounded step index, status, and short text summary.
#### Scenario: Renewal request includes an oversized or non-text summary
- **WHEN** a Host Agent submits a progress summary exceeding the configured length bound
- **THEN** the control plane truncates or rejects the oversized field without failing the underlying lease renewal