Context
Once Keystone has robot action catalogs and action request APIs, operators need a UI workflow to run pre-registered robot-side actions without typing commands or manually crafting API payloads.
Scope
- Add an action panel to the robot detail or operations view.
- Show available actions from the robot's current action catalog.
- Render argument inputs from the action schema.
- Require confirmation or approval flow for high-risk actions.
- Show recent execution status, result summaries, and failure reasons.
- Disable or clearly mark actions when the robot catalog is stale, the agent is offline, or the user lacks permission.
Acceptance Criteria
- Operators can select a robot action and submit valid arguments through the UI.
- Invalid arguments are blocked before submission where possible.
- High-risk actions require confirmation or approval according to the action definition.
- Recent action runs show status and sanitized result summaries.
- UI handles stale catalogs, offline robots, permission denial, and request creation failures.
Depends On
Context
Once Keystone has robot action catalogs and action request APIs, operators need a UI workflow to run pre-registered robot-side actions without typing commands or manually crafting API payloads.
Scope
Acceptance Criteria
Depends On