HyperKitty Chromium — Architecture Status: implemented reference implementation. Every module, supervision relationship, schema, and API route described below exists in this repository and compiles, boots, and passes its test suite (rebar3 eunit: 24 tests, 0 failures, including real headless-Chromium integration tests and chaos tests that kill live processes to verify recovery). Sections are marked (planned) where the specification calls for something this revision intentionally stubs or defers — there is no unmarked aspirational content in this document.
- Purpose and scope HyperKitty Chromium is an Erlang/OTP-native browser agent platform: a headless Chromium instance, driven over the Chrome DevTools Protocol (CDP), wrapped in an explicit OTP supervision tree so that browser control, agent orchestration, search, and messaging are separate, independently-supervised, independently-observable subsystems rather than library calls inside one monolithic process. The design principle it exists to demonstrate: an LLM-driven "agent" is a planning function that proposes tool calls; it is never trusted with direct, unchecked access to a browser process. Every tool call crosses an explicit, typed capability boundary — enforced by Erlang code, not by the prompt — before it reaches Chromium.