browser-agent-server 1.0.2__tar.gz → 1.0.3__tar.gz

browser_agent_server-1.0.3/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,33 @@
+name: Bug report
+description: Something in browser-agent-server or the browser-agent CLI misbehaves
+title: "[bug]: "
+labels: [bug]
+body:
+  - type: input
+    id: version
+    attributes:
+      label: Daemon version
+      description: Output of `browser-agent --version`
+      placeholder: browser-agent 1.0.2
+    validations:
+      required: true
+  - type: input
+    id: environment
+    attributes:
+      label: OS / how it runs
+      placeholder: Ubuntu 24.04, systemd unit, installed via `uv tool install`
+    validations:
+      required: true
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened vs what you expected
+      description: Include the exact command or HTTP request, and steps to reproduce if you have them
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: "`journalctl -u browser-agent -n 50 --no-pager` or the terminal output"
+      render: shell

browser_agent_server-1.0.3/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Companion project — @vernikr/browser-agent-mcp
+    url: https://github.com/vernikr/browser-agent-mcp
+    about: Issue with the MCP bridge or an MCP client, not the daemon itself? File it there.
+  - name: Docs
+    url: https://github.com/vernikr/browser-agent/tree/main/docs
+    about: Installation, systemd, API and troubleshooting guides

browser_agent_server-1.0.3/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,15 @@
+name: Feature request
+description: Suggest an idea for the daemon, CLI, or API
+title: "[feat]: "
+labels: [enhancement]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve for you?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution / API sketch

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/.github/workflows/ci.yml

@@ -4,6 +4,9 @@ on:
   push:
     branches: [main]
   pull_request:
+  schedule:
+    - cron: "17 5 * * 1"   # Mondays 05:17 UTC — catch bit-rotting deps early
+  workflow_dispatch:
 
 jobs:
   python:

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/.github/workflows/release.yml

@@ -49,6 +49,30 @@ jobs:
       - uses: pypa/gh-action-pypi-publish@release/v1
         if: steps.exists.outputs.exists == 'false'
 
+
+  deploy:
+    needs: pypi
+    runs-on: ubuntu-latest
+    environment:
+      name: prod
+      url: http://38.244.152.2:8765/status
+    steps:
+      # Plain ssh (no third-party action): this key is trusted to drive the prod host.
+      # Server side it is pinned to the single command via authorized_keys forced command:
+      #   command="/usr/local/bin/deploy-browser-agent",no-pty,no-port-forwarding,...
+      - name: Deploy exact version to production
+        env:
+          DEPLOY_SSH_KEY: ${{ secrets.DEPLOY_SSH_KEY }}
+          DEPLOY_HOST: ${{ secrets.DEPLOY_HOST }}
+          DEPLOY_USER: ${{ secrets.DEPLOY_USER }}
+        run: |
+          mkdir -p ~/.ssh && chmod 700 ~/.ssh
+          printf '%s\n' "$DEPLOY_SSH_KEY" > ~/.ssh/ci_deploy_key
+          chmod 600 ~/.ssh/ci_deploy_key
+          ssh-keyscan -H "$DEPLOY_HOST" >> ~/.ssh/known_hosts 2>/dev/null
+          VER="${GITHUB_REF_NAME#v}"
+          ssh -i ~/.ssh/ci_deploy_key "$DEPLOY_USER@$DEPLOY_HOST" "deploy $VER"
+
   github-release:
     needs: build
     runs-on: ubuntu-latest

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/CHANGELOG.md

@@ -5,6 +5,18 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.0.3] - 2026-10-10
+
+### Added
+
+- Continuous deployment: after a successful PyPI publish, `release.yml` deploys
+  the exact version to the production host over SSH. The CI key is pinned to a
+  single forced command (`deploy-browser-agent` on the server): it installs the
+  exact pinned version from PyPI via `uv tool`, restarts the unit and
+  health-checks `/status`, rolling back to the previous version on failure
+  (see docs/publishing.md → Continuous deployment).
+
+
 ## [1.0.2] - 2026-10-10
 
 ### Added

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: browser-agent-server
-Version: 1.0.2
+Version: 1.0.3
 Summary: Real headful Chrome on Xvfb with a hardware-level X11 mouse, Cloudflare Turnstile auto-solve and zero-leak CDP. Localhost HTTP API + CLI + Python SDK.
 Project-URL: Homepage, https://github.com/vernikr/browser-agent
 Project-URL: Repository, https://github.com/vernikr/browser-agent
@@ -23,6 +23,12 @@ Description-Content-Type: text/markdown
 
 # browser-agent
 
+[![PyPI](https://img.shields.io/pypi/v/browser-agent-server)](https://pypi.org/project/browser-agent-server/)
+[![CI](https://github.com/vernikr/browser-agent/actions/workflows/ci.yml/badge.svg)](https://github.com/vernikr/browser-agent/actions/workflows/ci.yml)
+[![Release](https://img.shields.io/github/v/release/vernikr/browser-agent)](https://github.com/vernikr/browser-agent/releases)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-blue)](https://pypi.org/project/browser-agent-server/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
+
 > 🔗 **Companion project:** [`@vernikr/browser-agent-mcp`](https://github.com/vernikr/browser-agent-mcp) — the MCP server that exposes this daemon to LLM agents (Claude Code, Cursor, Freebuff…). The two projects are developed together and speak the HTTP contract in [`docs/api.md`](docs/api.md).
 
 **Real headful Chrome on Xvfb with a hardware-level X11 mouse.** One localhost daemon gives any project, script, or AI agent on a Linux box a genuine desktop browser: steered over real XTEST input events on randomized Bézier paths, with zero-leak CDP (no `Runtime.enable`), Cloudflare Turnstile auto-solve, and RAM discipline for tiny VPSes (auto-hibernates to ~12 MB idle).

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/README.md

@@ -1,5 +1,11 @@
 # browser-agent
 
+[![PyPI](https://img.shields.io/pypi/v/browser-agent-server)](https://pypi.org/project/browser-agent-server/)
+[![CI](https://github.com/vernikr/browser-agent/actions/workflows/ci.yml/badge.svg)](https://github.com/vernikr/browser-agent/actions/workflows/ci.yml)
+[![Release](https://img.shields.io/github/v/release/vernikr/browser-agent)](https://github.com/vernikr/browser-agent/releases)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-blue)](https://pypi.org/project/browser-agent-server/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
+
 > 🔗 **Companion project:** [`@vernikr/browser-agent-mcp`](https://github.com/vernikr/browser-agent-mcp) — the MCP server that exposes this daemon to LLM agents (Claude Code, Cursor, Freebuff…). The two projects are developed together and speak the HTTP contract in [`docs/api.md`](docs/api.md).
 
 **Real headful Chrome on Xvfb with a hardware-level X11 mouse.** One localhost daemon gives any project, script, or AI agent on a Linux box a genuine desktop browser: steered over real XTEST input events on randomized Bézier paths, with zero-leak CDP (no `Runtime.enable`), Cloudflare Turnstile auto-solve, and RAM discipline for tiny VPSes (auto-hibernates to ~12 MB idle).

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/docs/publishing.md

@@ -30,3 +30,22 @@ Then still tag, so the GitHub Release and CHANGELOG stay in sync: `git tag vX.Y.
 - Verify: https://pypi.org/pypi/browser-agent-server/json (`info.version`)
 - Bump CHANGELOG under `[Unreleased]` for the next cycle.
 - Revoke the manual token once trusted publishing is proven (pypi.org → Account settings → API tokens).
+
+## Continuous deployment (release → production)
+
+After the PyPI job succeeds, `release.yml` also runs a `deploy` job that ships the exact
+tag version to the production host — no human SSH needed. Design:
+
+- The repo holds three secrets: `DEPLOY_SSH_KEY` (dedicated ed25519 keypair), `DEPLOY_HOST`,
+  `DEPLOY_USER`. The key is **not** the admin key; on the server it is pinned in
+  `authorized_keys` to a single forced command:
+  `command="/usr/local/bin/deploy-browser-agent",no-pty,no-port-forwarding,no-agent-forwarding,no-X11-forwarding`.
+  Even if the GitHub secret leaks, it can only redeploy this one daemon.
+- The server-side script accepts only `deploy <semver>` (anything else is rejected), installs
+  `browser-agent-server==<ver>` from PyPI (`uv tool install --force --refresh`, with retries
+  for registry propagation), restarts the systemd unit and waits for `/status` to report the
+  target version. On healthcheck failure it reinstalls the previous version and restarts again.
+- Idempotent: redeploying the version already running is a no-op success.
+
+One-time setup on a new host: install `uv` + the package, create/pin the key as above, put the
+three secrets into the repo (Settings → Secrets and variables → Actions), done.

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "browser-agent-server"
-version = "1.0.2"
+version = "1.0.3"
 description = "Real headful Chrome on Xvfb with a hardware-level X11 mouse, Cloudflare Turnstile auto-solve and zero-leak CDP. Localhost HTTP API + CLI + Python SDK."
 readme = "README.md"
 requires-python = ">=3.12"

{browser_agent_server-1.0.2 → browser_agent_server-1.0.3}/uv.lock

@@ -13,7 +13,7 @@ wheels = [
 
 [[package]]
 name = "browser-agent-server"
-version = "1.0.2"
+version = "1.0.3"
 source = { editable = "." }
 dependencies = [
     { name = "trafilatura" },