browser-use--browser-harness
Saurav Panda
2ce5b870c1
http_get called urllib.request.urlopen with no explicit SSL context, so it fell back to whatever trust store the interpreter shipped with. On python.org's Python 3.11 for macOS the CA keychain is empty until the user runs Install Certificates.command, which nobody does — every HTTPS call raised CERTIFICATE_VERIFY_FAILED. Agents were then writing domain-skills that suggested subprocess curl or, worse, disabling TLS verification entirely. Load certifi's bundle explicitly via ssl.create_default_context. Same approach requests and httpx use, works across macOS/Linux/Windows and across Python installers.
22 行
508 B
TOML
22 行
508 B
TOML
[build-system]
|
|
requires = ["setuptools>=69"]
|
|
build-backend = "setuptools.build_meta"
|
|
|
|
[project]
|
|
name = "harness"
|
|
version = "0.1.0"
|
|
description = "The simplest, thinnest, and most powerful harness to control your real browser with your agent."
|
|
requires-python = ">=3.11"
|
|
dependencies = [
|
|
"browser-harness>=0.0.1",
|
|
"cdp-use>=1.4.5",
|
|
"certifi>=2024.2.2",
|
|
"websockets>=16.0",
|
|
]
|
|
|
|
[project.scripts]
|
|
browser-harness = "run:main"
|
|
|
|
[tool.setuptools]
|
|
py-modules = ["run", "helpers", "daemon", "admin"]
|