The one place an AI worker is allowed to touch a system it does not own — and the one place that touch leaves a record.
Sessions live in the browser's vault, scoped per site, revocable without changing a password. A worker asks the browser to act; it never receives a cookie, a token or a password. Credentials do not pass through a prompt — which is where every leak in this category comes from.
What must be true before, the exact action, what must be true after, the evidence, and whether it can be undone — declared before the click and checked after it. An action whose postconditions fail is a rollback, not a shrug.
The same task, seen enough times, stops being a model call and becomes a recipe. The browser gets cheaper at what it does often, instead of paying full price for the same click forever.
Solace Browser is a Chromium build, so the web works the way you expect. The additions are a credential vault, a debugging bridge workers connect to, and hardening for the crashes that take stock Chromium down in a long-running session.
| Platform | Architecture | |
|---|---|---|
| macOS | Apple silicon (arm64) | soon |
| macOS | Intel (x86_64) | soon |
| Windows | x86_64 | soon |
| Linux | AppImage (x86_64) | soon |
| Linux | .deb (x86_64) | soon |
Builds are not published yet. They ship signed — notarized on macOS, Authenticode on Windows — or they do not ship. A browser that asks to be trusted with your sessions does not arrive as an unsigned binary.
The browser is the hands. Buzz is the room. Solace AGI is the mind. A worker that cannot act is a chatbot; a worker that acts without a record is a liability.