Browser Automation Task Review with Claude Code: API Runtime Pattern
A production playbook for browser automation task review in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Automation platform teams
The problem
Automation platform teams need browser automation task review to run repeatedly against recorded browser steps, DOM snapshots, and output requirements. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the browser automation task review instructions as a skill, send recorded browser steps, DOM snapshots, and output requirements as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For browser automation task review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=browser-automation-task
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo