browserhive@0.1.3

Patch Changes

• #13 3752bc9 Thanks @arg1998! - Dashboard: links to the documentation on browserhive.ai, the website and GitHub.

  • A Help menu in the top bar opens the guide for the current page, the dashboard guide, MCP client setup, troubleshooting, release notes and issue reporting.
  • The sidebar footer links to Docs, GitHub and the website, and the version links to its release notes.
  • The command palette can open the docs, the tool reference, the website and GitHub.
  • Info popovers are fixed: inline code and bold text no longer break onto their own lines. They now have paragraph spacing and a "Read the docs" link.
  • New explainers were added across Overview, Websites, Vault, Vault log, System (tokens, configuration, storage, migrations, degradations) and session details.
  • System setting hints now use the real camelCase flags (--maxSessions, --allowEvaluate, --retentionDays) and link to each key in the configuration reference.

browserhive@0.1.2

Patch Changes

• #9 52929f9 Thanks @arg1998! - The npm package homepage now points at https://browserhive.ai.

browserhive@0.1.1

Patch Changes

• #5 1bd3de0 Thanks @arg1998! - Point README, changelog, and dashboard documentation links at the real repository, github.com/arg1998/BrowserHive.

browserhive@0.1.0

Minor Changes

Initial release of BrowserHive, a local Model Context Protocol server that runs isolated, observable Chromium sessions for AI agents.

• MCP server (official SDK) with 43 browser tools over Streamable HTTP or stdio: session lifecycle, navigation, page interaction, content and snapshots, tabs, cookies and storage, downloads and uploads, saved logins, attention and vault. Tools carry titles, annotations and outputSchema/structuredContent; failed calls return the [CODE] message text with the structured error in _meta["browserhive.ai/error"].
• Runs on Bun ≥ 1.4. MCP, the admin REST API, the realtime WebSocket and the dashboard share one port (127.0.0.1:9876 by default); non-loopback binds require bearer tokens.
• Each session is its own Chromium process and browser context, with a sliding lease, memory or persistent profiles, and per-principal ownership on every tool.
• Admin dashboard (React 19): sessions with live view and human takeover, timeline, websites, blocklist with hot reload, vault, logs, system status and persisted notifications.
• Human attention: request_attention hands the page to an operator and blocks until it is resolved, with timeouts and a configurable minimum wait.
• Vault credential injection through Bitwarden: bindings and folder policies stored in the database, origin, session and principal checks, optional confirmations with deadlines, redacted tool results, credential typing excluded from Playwright traces, and one audit row per fill.
• Stealth: full Chromium in new-headless mode, Patchright when installed, automation signals removed, a coherent identity derived from the host, optional display fingerprint and human-like input.
• One configuration schema: every key works as a camelCase CLI flag, a BROWSERHIVE_* environment variable and a browserhive.config.json key, with precedence defaults < env < file < CLI, shadow logging, "did you mean" hints and fail-fast validation.
• CLI: serve (default), init (installs Chromium; nothing is downloaded at install time), doctor, purge, config show|schema|validate, db status|backup|restore|migrate, admin reset-password, admin tokens list|create|revoke.
• SQLite storage via bun:sqlite with forward-only migrations, automatic pre-migration backups and a downgrade compatibility window (DB_NEWER_THAN_BINARY, db restore).
• Operator authentication with Argon2id, a one-time seed password and forced change; hashed bearer tokens for agents.
• Opt-in OpenTelemetry export of traces, metrics and logs over OTLP/HTTP.
• Configurable recording (--recordToolResults full|shape|none) and retention; cookie values are never stored and URL query strings are stripped unless allow-listed.
• Programmatic API: createServer() with typed configuration, error codes and tool contracts.