Module chrome 

Protocol-facing DTOs for the chrome/* app-server methods.

The shared browser-bridge contract lives in roder_api::chrome; the status and tab/browser/permission record types are re-exported here so SDK clients and the app-server handlers share one definition. The request param structs below describe the JSON-RPC payloads accepted by AppServer.

Browser page content, console output, and network metadata forwarded through these methods are untrusted: dispatch results are passed through verbatim as opaque serde_json::Value and must not be treated as instructions.

Structs

ChromeBrowser

A browser the extension can drive (Chrome is P0, Edge is P1).

ChromeCommand

A command Roder asks the extension to run. kind is the wire type (e.g. "page/snapshot"); params is merged into the outgoing frame.

ChromeDebugReadParams

Params for chrome/debug/console and chrome/debug/network.

ChromeEnableParams

Params for chrome/enable. Optionally sets the permission mode.

ChromeNavigateParams

Params for chrome/tabs/navigate.

ChromePageActionParams

Params for chrome/page/action.

ChromePageSnapshotParams

Params for chrome/page/snapshot.

ChromePermissionsListParams

Params for chrome/permissions/list.

ChromePermissionsUpdateParams

Params for chrome/permissions/update.

ChromeSetModeParams

Params for chrome/setMode.

ChromeSitePermission

Per-origin site permission record stored by the extension.

ChromeStatus

Snapshot of the connection, mirrored to TUI/CLI/SDK clients via chrome/status.

ChromeTab

A tab visible to the extension.

ChromeTabActivateParams

Params for chrome/tabs/activate.

Enums

ChromeError

Failure surface for browser commands.

ChromePermissionMode

How aggressively Roder may act in the browser on the user’s behalf.