Skip to content

Make verbose diagnostics effective across hosted, browser, and auth commands #174

Description

@rishabhraj36

Parent: #171

Problem

-v/--verbose is documented as universal, but support is inconsistent and hosted adapter execution currently accepts the flag without using it.

Verified gaps:

  • Hosted adapter parsing accepts -v, but dispatch drops parsed.verbose (src/hosted/runner.ts:269-307).
  • The hosted client execution contract has no verbose field (src/hosted/client.ts:103-114).
  • Browser leaves reject -v, although CDP diagnostics already read WEBCMD_VERBOSE (src/browser/cdp.ts:119-123, 354-359).
  • auth status and auth refresh perform browser/daemon probes but reject -v.
  • doctor already supports -v.

Scope

  • Forward hosted adapter verbose mode and make its effect observable, or reject it instead of silently ignoring it.
  • Expose/apply verbose mode for browser leaves that perform bridge/CDP I/O.
  • Exclude filesystem-only browser init.
  • Decide explicitly whether browser verify -v forwards to its adapter subprocess.
  • Add verbose support to auth probes only if useful underlying diagnostics are wired through.
  • Do not add no-op verbose flags to list-only, filesystem-only, completion, acknowledgement-only, or passthrough commands.

Acceptance criteria

  • Hosted -v is effective or explicitly unsupported.
  • Browser -v enables existing bridge/CDP diagnostics.
  • Any auth -v support has observable diagnostics.
  • No command advertises a no-op verbose flag.
  • Local and hosted behavior is covered by tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions