The published @poe-platform/safe-bash@0.1.636 registers playwright-cli, but its standard discovery path is missing.
Reproduction using the real package CLI plugin (no browser allocation is needed):
Actual result: exit code 1 and playwright-cli: Unsupported option: --help on stderr. playwright-cli help is also rejected as an unsupported command by parseInvocation.
Expected: playwright-cli --help succeeds without a browser and describes the standard command names, arguments, options and supported subset. Help should explain named sessions (-s / --session, PLAYWRIGHT_CLI_SESSION, default session), session reuse/lifecycle, tabs, snapshot refs, screenshot/snapshot output options, and unsupported operations. Command-specific help should work where the standard CLI supports it.
Please keep the familiar upstream Playwright CLI syntax; this request is for library-owned standard help, not a host-specific API, renamed commands, or custom help wrapper. The user integrating this in Poe explicitly wants agents to discover behavior through playwright-cli --help, rather than duplicate a command reference in the tool description or prompt.
Source evidence: dist/safe-bash/commands/playwright/index.js forwards all args directly into the controller, and dist/safe-bash/playwright/invocation.js rejects --help before command dispatch. Regression coverage should assert exit 0, help output describing session selection, and zero browser acquisitions, both with and without a configured browser adapter.
Related separate capability gap: #733 (snapshots omit readable page text and native form labels).
The published
@poe-platform/safe-bash@0.1.636registersplaywright-cli, but its standard discovery path is missing.Reproduction using the real package CLI plugin (no browser allocation is needed):
Actual result: exit code 1 and
playwright-cli: Unsupported option: --helpon stderr.playwright-cli helpis also rejected as an unsupported command byparseInvocation.Expected:
playwright-cli --helpsucceeds without a browser and describes the standard command names, arguments, options and supported subset. Help should explain named sessions (-s/--session,PLAYWRIGHT_CLI_SESSION, default session), session reuse/lifecycle, tabs, snapshot refs, screenshot/snapshot output options, and unsupported operations. Command-specific help should work where the standard CLI supports it.Please keep the familiar upstream Playwright CLI syntax; this request is for library-owned standard help, not a host-specific API, renamed commands, or custom help wrapper. The user integrating this in Poe explicitly wants agents to discover behavior through
playwright-cli --help, rather than duplicate a command reference in the tool description or prompt.Source evidence:
dist/safe-bash/commands/playwright/index.jsforwards all args directly into the controller, anddist/safe-bash/playwright/invocation.jsrejects--helpbefore command dispatch. Regression coverage should assert exit 0, help output describing session selection, and zero browser acquisitions, both with and without a configured browser adapter.Related separate capability gap: #733 (snapshots omit readable page text and native form labels).