41 lines
2.7 KiB
Markdown
41 lines
2.7 KiB
Markdown
# host-agent-console-task-pages Specification
|
|
|
|
## Purpose
|
|
Define the authenticated, same-origin task-history views served by the Host
|
|
Agent local console.
|
|
|
|
## Requirements
|
|
|
|
### Requirement: Host Agent local console exposes step-level status for the current assignment
|
|
The Host Agent's local console SHALL display, for its currently executing assignment, the current step index, step status, and a short summary, sourced from the Host Agent's local task metadata store, refreshed on the console's existing polling interval.
|
|
|
|
#### Scenario: An assignment is currently executing
|
|
- **WHEN** an operator views the Host Agent local console dashboard while an assignment is executing
|
|
- **THEN** the dashboard shows the current step index, step status, and a short summary for that assignment, updating on subsequent polls
|
|
|
|
#### Scenario: No assignment is currently executing
|
|
- **WHEN** an operator views the dashboard while the Host Agent is idle
|
|
- **THEN** the dashboard shows no in-progress step information
|
|
|
|
### Requirement: Host Agent local console exposes read-only task history with per-step detail and screenshots
|
|
The Host Agent's local console SHALL provide authenticated, read-only pages listing recently executed tasks and, for a selected task, its full per-step history including any captured screenshots, sourced from the Host Agent's local task metadata store and timeline.
|
|
|
|
#### Scenario: Operator lists recent tasks
|
|
- **WHEN** an authenticated operator opens the Host Agent local console's task list page
|
|
- **THEN** it shows tasks from the local task metadata store, most recent first, including tasks that have already reached a terminal state
|
|
|
|
#### Scenario: Operator inspects a completed task's step history
|
|
- **WHEN** an authenticated operator opens the detail page for a specific completed task
|
|
- **THEN** the page shows each recorded step in order, including its tool call, result, and any captured screenshot
|
|
|
|
#### Scenario: Unauthenticated request
|
|
- **WHEN** a request to the task list or task detail pages is made without a valid Host Agent console session
|
|
- **THEN** the Host Agent rejects the request the same way it rejects unauthenticated requests to its other console pages
|
|
|
|
### Requirement: Host Agent local console task pages require no new cross-origin surface
|
|
The Host Agent local console's task pages SHALL be served same-origin from the Host Agent's existing web application, without introducing new CORS allowances or a dependency on the separate Runtime `console/` frontend.
|
|
|
|
#### Scenario: Task pages are requested
|
|
- **WHEN** an operator's browser requests the Host Agent local console's task pages
|
|
- **THEN** the pages are served by the Host Agent's own application using its existing session/CSRF protections, with no additional cross-origin configuration required
|