Skip to main content
Change of provenance

The repository or configuration that created this release differ from a previous release. View details.

browser-daemon-client

Async Python client for browser-daemon, with nothing but aiohttp: made for Home Assistant integrations and other code that cannot carry Playwright.

import aiohttp
from browser_daemon_client import BrowserDaemon, RunError, step

async with aiohttp.ClientSession() as http:
    bd = BrowserDaemon(
        http, "https://browser.example.org", secret, client="Home Assistant · HR WORKS"
    )
    try:
        res = await bd.run(
            profile="work",
            url="https://hr.example.org/login",
            steps=[
                step.fill("#user", arg="user"),
                step.fill("#password", arg="password"),
                step.click("role=button[name='Sign in']"),
                step.wait_for(".dashboard"),
                step.text(".balance", as_="balance"),
            ],
            args={"user": user, "password": password},
        )
    except RunError as err:
        print(err, err.run.url)  # err.run.screenshot: the tab, as a base64 PNG
    else:
        print(res.result["balance"])
  • run(): a Playwright script (a JavaScript function expression) or steps, in a profile's browser, a session or a throwaway browser. Runs for a profile go to the node that has it. See docs/run.md.
  • overview(), find_profile(), sessions(), session(), create_session(), delete_session(), set_idle_timeout(), tabs(), open_tab(), close_tab(), export_auth() (a page's cookies and storage; never log them).
  • node= sends a request to another node of the mesh through this one.
  • read_secret() reads the cluster secret from its file.

Errors are BrowserDaemonError (with status), and for runs RunError and RunTimeout (with the whole answer in .run).

Releasing

The client has the daemon's version and is released with it: just release-prepare X.Y.Z bumps pyproject.toml with Cargo.toml, and the signed vX.Y.Z tag makes the python job of the release workflow publish it to PyPI through trusted publishing (the pypi environment; no token is stored anywhere). test.yaml tests it on every change.

Metadata

Release files for browser-daemon-client 0.11.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Change of provenance

The repository or configuration that created these release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Source distribution (sdist)

Source distribution for browser-daemon-client 0.11.0
File Size Uploaded Provenance Actions
browser_daemon_client-0.11.0.tar.gz 7.4 kB With provenance Details for browser_daemon_client-0.11.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for browser-daemon-client 0.11.0
File Interpreter ABI Platform Actions
browser_daemon_client-0.11.0-py3-none-any.whl Python 3 none any Details for browser_daemon_client-0.11.0-py3-none-any.whl

Total release size: 13.7 kB

Release files / browser_daemon_client-0.11.0.tar.gz

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL browser_daemon_client-0.11.0.tar.gz
Size 7.4 kB
Tags Source
SHA-256 checksum
How to use checksums
53049d263fa64e71b1e865ddd1aca359aacbfe463cf7de29db4cb6684523e0a3
BLAKE2b-256 checksum
How to use checksums
8116a0fbe4f5629c7efa7a32feca53b45fc631bcd3840982ffdc4c3bf1bfad45
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Release files / browser_daemon_client-0.11.0-py3-none-any.whl

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL browser_daemon_client-0.11.0-py3-none-any.whl
Size 6.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6656ef55dae91cd7403f480fd45616c9162d70311789ccb4e08b4a0bdaf2dbf0
BLAKE2b-256 checksum
How to use checksums
3b3d9fdd71b9036791c10e6db32aa32ce137c2d9ad88cc8cc4002dfb479d516c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Security for browser-daemon-client 0.11.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Change of provenance

The configuration that created this release differs from a previous release.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Select from 2 files

Attestation for browser_daemon_client-0.11.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page