browser-use--browser-harness
8a0c981082
- Add --version, --doctor, --setup, --update[-y] commands in run.py; logic lives in admin.py (install-mode detection, GitHub-releases cache with 24h TTL, dirty-worktree guard, interactive Chrome-attach flow). - Print a once-per-day startup banner telling agents to run `browser-harness --update -y` when a newer release is available. - Rename project to browser-harness in pyproject.toml so PyPI installs (uv tool install browser-harness) work via the public package name. - Add .github/workflows/release.yml: on v* tag push, verify the tag matches pyproject.toml, uv build, and publish to PyPI via trusted publishing. - Wire helpers.http_get through fetch_use.fetch_sync(...).text when BROWSER_USE_API_KEY is set; falls back to the original urllib path otherwise, preserving the existing str return contract. - Document the new commands and the agent's self-update duty in SKILL.md and install.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
21 行
485 B
TOML
21 行
485 B
TOML
[build-system]
|
|
requires = ["setuptools>=69"]
|
|
build-backend = "setuptools.build_meta"
|
|
|
|
[project]
|
|
name = "browser-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 = [
|
|
"cdp-use==1.4.5",
|
|
"fetch-use==0.4.0",
|
|
"websockets==16.0",
|
|
]
|
|
|
|
[project.scripts]
|
|
browser-harness = "run:main"
|
|
|
|
[tool.setuptools]
|
|
py-modules = ["run", "helpers", "daemon", "admin"]
|