Claws
Agent toolchain discovery, planning, dry-run, validation, trace, and handoff harness.
Validate Claws in BrowserOps
Preview the plan publicly or launch the trusted-domain browser check using the server-side Vercel PLATPHORM_API_KEY when no key is entered.
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
404degraded
trace echoed
Browserbase Runtime
Protected 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 require PLATPHORM_API_KEY.
Handoff Examples
Claws remains the planning/remediation harness; BrowserOps attaches browser-visible evidence.