Claws
Agent toolchain discovery, planning, dry-run, validation, trace, and handoff harness.
Validate Claws in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Claws's product role.
- Target
- https://claws.platphormnews.com
- Journey
- Vercel alias snapshot homepage smoke
Held in memory only and sent in the authorization header.
Boundary
Public preview validates intent. Cloudflare runs create real browser evidence. Downstream delivery is tracked as a handoff and is never marked accepted without a response.
Integration run state
Preview the BrowserOps plan publicly, then use the operator key for a protected Cloudflare browser check.
Live Public Connectivity
Fix Claws public health, docs, LLMS, or MCP discovery before treating this integration as ready.
health
no responsefailed
trace echo not confirmed
apiDocs
200passed
trace echoed
llms
200passed
trace echoed
mcp
200passed
trace echoed
handoffReceiver
no responsedegraded
trace echo not confirmed
Cloudflare Browser Runtime
BrowserOps runs for Claws use cloudflare-browser-run. Cloudflare is configured; D1 stores run metadata and R2 stores artifacts. Session metadata records BrowserOps run ID, journey ID, and target service without storing credentials.
Capability Mapping
BrowserOps may call
- read_agent_plan
- read_dry_run_state
BrowserOps may receive
- agent_plan_browser_verification_requested
Transport and Boundary
- Preferred transports
- mcp, openapi, trace
- API docs
- https://claws.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public plan templates may be readable; remediation and delegated execution use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
Claws remains the planning/remediation harness; BrowserOps attaches browser-visible evidence.