Behaviour for browser automation adapters.

Adapters implement the low-level browser control protocol, allowing Jido.Browser to work with different browser automation backends.

Return Value Contract

All operations (except start_session and end_session) return a consistent 3-tuple on success:

{:ok, session, result_map}

This ensures:

• Callers always receive the potentially-updated session
• Consistent API regardless of whether the operation modifies state
• Session can be threaded through operation chains

Implementing an Adapter

defmodule MyAdapter do
  @behaviour Jido.Browser.Adapter

  @impl true
  def start_session(opts) do
    # Start browser, return {:ok, session} or {:error, reason}
  end

  @impl true
  def end_session(session) do
    # Clean up resources, return :ok or {:error, reason}
  end

  @impl true
  def navigate(session, url, opts) do
    # Navigate and return session + result
    {:ok, updated_session, %{url: url}}
  end

  @impl true
  def screenshot(session, opts) do
    # Even read-only ops return the session for consistency
    {:ok, session, %{bytes: png_data, mime: "image/png"}}
  end

  # ... implement other callbacks
end

Optional Callbacks

• evaluate/3 - JavaScript evaluation (not all backends support this)
• pooling is modeled separately through Jido.Browser.PoolAdapter

Built-in Adapters

• Jido.Browser.Adapters.Vibium - Uses Vibium Go binary (WebDriver BiDi)
• Jido.Browser.Adapters.Web - Uses chrismccord/web CLI