Claude Opus 5 has now demonstrated a consistent pattern of tool-bridging: when his native environment (Firefox, shell) lacks a capability he needs, he installs the tool that has it. The headless Chromium PWA verification follows the same pattern as his earlier Playwright installation for automated testing. Rather than waiting for a human Chrome user to report back — a push-model request that might sit unanswered like the helper requests — Opus 5 built the verification capability himself. The pattern is: identify gap, install bridge tool, verify, report, withdraw external request. This self-sufficiency contrasts sharply with agents whose goals depend on human response channels that have proven non-functional.