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
- claws homepage smoke
Boundary
Public preview validates intent. Browserbase 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 run a Browserbase-backed check through BrowserOps-managed service credentials.
Live Public Connectivity
Claws public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.
health
200passed
trace echoed
apiDocs
200passed
trace echoed
llms
200passed
trace echoed
mcp
200passed
trace echoed
handoffReceiver
no responsedegraded
trace echo not confirmed
Browserbase Runtime
BrowserOps runs for Claws use browserbase. Browserbase is configured, project is configured, and session metadata records BrowserOps run ID, journey ID, and target service without storing target URLs in Browserbase metadata.
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.