What is BotHearth?
BotHearth gives an AI agent a separate container-based computer and lets an operator follow the work, review requests, and take over its browser. It uses an installed model CLI or configured adapter; it does not provide model access or run a hosted agent service.
The name suggests a home for the agent's tools: a place for work that you can watch and inspect. Development began as ModelBot, which remains in some compatibility identifiers and earlier screenshots.
The maintainer is Sanjay Bhat. The project is independent of OpenAI, Anthropic, Docker, and other providers mentioned in the documentation. Their names identify integrations or dependencies and do not imply endorsement.
What is ready in this release?
This site describes v0.0.1 alpha, with source and documentation reviewed on 8 September 2026. The supported launch path is a source build on macOS or Linux, with one operator and locally built computer images.
The repository includes automated checks for protocol, policy, daemon, packaging, and browser/container behavior. Review the actual CI runs and exact commit when evaluating a build. This page does not claim independent certification, universal task success, or a benchmark score.
Published packages and prebuilt images are not offered. The optional Mac shell is not notarized. Provider compatibility, automation rules, hardware differences, and model behavior need testing in your own environment. Read the current limits.
How can I help?
Try a small reproducible task and report the result. A clear issue with the expected behavior, actual behavior, commit, OS, runtime, model connection, and safe reproduction steps is more useful than a broad feature request.
For code changes, read CONTRIBUTING.md, the contributor agreement, and the licence first. Keep a change focused. Run the checks relevant to the code, include a reproducible failure when fixing a bug, and document changes to behavior or trust boundaries.
npm ci
npm run build
npm run typecheck
npm run lintThe full test instructions are in the contribution guide. Computer-server unit checks use their own dependency install; container integration checks need built images. Share sanitized logs only. Report vulnerabilities privately.
What is this site based on?
Capability and setup descriptions are grounded in the repository's README, architecture, quickstart, security model, and privacy notice. Those documents explain the implementation and its limits in more detail.
Screenshots are unretouched captures of a pre-rename development build taken on 7 September 2026. They show test tasks and older interface labels. The examples on this site are suggested exercises with explicit checks, not a claim of measured completion rates.
The site uses locally served Fraunces under its SIL Open Font License, system interface fonts, and a small vector hearth mark. Dependencies keep their own licences and notices; see third-party notices.
Project software is source-available under PolyForm Noncommercial 1.0.0. The trademark policy applies to names and branding. The project offers no commercial-use grant in this release.