Overview

Bloosh is an OS Agent: a named assistant that keeps a ranked day, a calendar it can write to, a memory of your people and work, and the documents you give it. This documentation covers how the product is put together and how to use it.

#What you get

A Bloosh workspace is one organisation. Everyone in it shares the same assistant configuration, the same document library, and the same calendar connections you choose to attach.

• Priorities — a seven-day rail of what to do next, rebuilt as the day moves.
• Calendar — a week view the agent can propose blocks on, two-way with Google or Microsoft.
• Chat — a persistent thread with an assistant you name, and a memory of the people and deals behind the work.
• The Librarian — uploaded files indexed so the agent can answer from your material and cite which file it read.

Outbound mail, calendar writes and deletions always come back as a card. Nothing leaves the workspace until you confirm it.

#How to read these docs

Start with Quickstart if you have not signed in yet. The Products section describes each surface. Reference lists connections, models and plans.

#Workspace isolation

Each organisation is isolated in the database. Members see only what their organisation holds. Invites, billing and connections are scoped to that workspace — see Workspace and Security.