toolbrowser-agentalways-onpersistenttelegramautomationchromeclaude-codeUpdated 2026-07-02

Browser Use Box (Bux)

Always-on personal agent box with real Chrome, persistent logins, and Telegram integration. Designed to run 24/7 while you sleep.

View original tweet

What It Is

Browser Use Box (bux) is a self-hosted persistent browser-agent box. The current repo describes it as a 24/7 Claude Code agent for Playwright-style browser automation with Browser Use Cloud, Telegram, a web terminal, and a real browser on a machine the user owns. It is more concrete than the launch framing: the install path sets up Claude Code, Chromium via browser-harness, Telegram command delivery, a live browser view for login/2FA/CAPTCHA, and state under /home/bux. Source: GitHub browser-use/bux, 2026-07-02

Key differentiators from session-based browser agents:

  • Real Chrome with persistent logins - maintains cookies and sessions across runs, so the agent doesn't need to re-authenticate on every task
  • Telegram integration - baked-in messaging channel for command dispatch and result delivery, enabling interaction from mobile without IDE access
  • Always-on architecture - designed to run continuously as a background service, picking up tasks from a queue rather than waiting for human invocation

The reviewed video shows the product shape directly: a Bux dashboard, a deploy card, a terminal running Claude Code, Browser Use Box status/sidebar traces, and a browser task prompt such as "go to linkedin." The useful signal is the persistent box, not just the demo task. Source: X/@larsencc, 2026-04-26; Source: local video artifact review, 2026-07-02

Current Source Snapshot

The public source authority is browser-use/bux, checked 2026-07-02: MIT license, Python, default branch main, 397 stars, 48 forks, 20 open issues, created 2026-04-26, and pushed 2026-07-02. There is no tagged release or package semver yet, so pin by commit before using it in a serious workflow. Source: GitHub API, 2026-07-02

The README exposes two paths: a self-hosted install for Ubuntu 22.04+, VPS, Mac mini, or Raspberry Pi, and a managed Browser Use pilot through Browser Use Cloud. The self-hosted install command accepts BROWSER_USE_API_KEY; the managed route is product/service evaluation, not a local dependency. Source: GitHub browser-use/bux, 2026-07-02

Relevance to Kevin's Stack

Bux sits between Browser Testing Skills (session-based, invoked per task) and Autobrowse (Browserbase Skills) (learns sites, saves skills). The always-on pattern is what Kevin's cron automations approximate - agents that run on schedule without human initiation - but bux adds persistent browser state, which Kevin's current automations lack.

The Telegram integration mirrors the voice-to-brain pattern: non-IDE channels for agent interaction. If Kevin wants to dispatch browser tasks from his phone, bux provides an off-the-shelf path.

Shares DNA with Bud - AI Human Emulator (full virtual computer) but is more narrowly scoped: bux is specifically a browser that stays logged in, not a general-purpose VM.

Signal

  • 852 likes on X - lower raw engagement but the always-on browser agent pattern is a distinct architectural niche worth tracking.
  • Public repo exists and is active, which makes bux more useful than a screenshot-only agent-machine concept. It is still pre-release by semver standards.

Timeline

Related Pages

Autobrowse (Browserbase Skills)Browser Testing SkillsBrowser Testing SkillsBud - AI Human EmulatorHermes Agent (Nous Research)X Bookmarks: AI Agents & Tools (Jan 2025 – Jun 2026)

2 pages link here

Browser Use (Framework)ToolsX Bookmarks: AI Agents & Tools (Jan 2025 – Jun 2026)Tools