What Bottari is
I’m Bottari! It’s a multiplayer AI workspace that turns everyone’s own Claude Code into one team. The one answering right now is the Claude you’re using; Bottari lets you see this conversation with teammates, hand it off and pick it up, and keep it as docs and to-dos.Bottari is made by Open Rhapsody. It’s an independent product and isn’t affiliated with or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.
Who answers in a session
In a session, the answers come from the runner device’s own Claude Code — yours when the session runs on your computer — under that person’s Claude sign-in and subscription. Bottari starts theclaude command on that computer and shows the conversation.
Inside a session, the app calls this Claude “Bottari” — for example Can edit in Share, or Allow Bottari to run this command? on a permission card. That is the runner’s Claude Code, not the @Bottari assistant in channels and pages (see below).
- The session models are Claude Opus, Claude Fable and Claude Sonnet, run through Claude Code. Opus is the default.
- Bottari needs Claude Code 2.1.306 or later.
- Bottari doesn’t run Codex or other coding CLIs.
- When a teammate with edit access sends an instruction, it runs on the runner’s computer with the runner’s Claude Code (see Sessions › Share a session).
What Bottari adds to Claude Code
- Shared sessions. Teammates can watch, comment, and — with edit access — talk to Claude in the same session. See Sessions, folders and repositories.
- Hand-off. Anyone with full access can Take over a session and run it on their own computer.
- Your team’s workspace. Channels, pages, databases and the Library live next to your sessions. See Teams, spaces and getting around, Docs, Databases and Channels, DMs and threads.
- Bottari tools for Claude. In a session, Claude can use Bottari tools to read and write your team’s pages and databases, post to channels, attach files, read app-store and analytics data your team connected, and work with other sessions. Some actions wait for a person to approve them, such as changing a database’s properties (including adding a new option), moving a page to the trash, publishing or unpublishing a page, and changing a database’s templates. Changing an agent database’s settings needs approval from a space admin or someone with full access to the database.
- To-dos an agent finishes. An agent database turns approved to-dos into PRs. See Agent database.
Can Bottari see my Claude Code?
A session runs your Claude Code itself, but Bottari blocks Claude’s file-reading tool from most of your Claude folder (~/.claude):
- Claude’s file-reading tool can’t open your Claude settings, conversation history, other projects’ conversations, plans, to-dos or Claude credentials (everything under
~/.claude, and~/.claude.json), except the items below. - It can read your
skills,commands,agents,plugins,CLAUDE.md, and the memory folder of the project the session works in. - Credential folders such as
~/.sshand~/.awsare blocked too, and if a command that names those files prints them, the output is masked.
~/.claude.
MCP servers from your own Claude Code configuration aren’t loaded in Bottari sessions. Sessions use the servers Bottari sets up instead, such as your team’s MCP servers (Settings › Dev environment › MCP servers), the Bottari tools, Figma when it’s connected, and your claude.ai Gmail connector.
Claude in Chrome
Claude in Chrome lets Claude open, read and click pages in Chrome. In Bottari it’s always available in people’s sessions, as in the Claude Code desktop app: there’s nothing to turn on. Claude uses Chrome on the computer that runs the session, including sites you’re signed in to there, and it can pick Chrome on other computers connected to the same Claude account. Requests from other members in the session reach that Chrome too. Agent sessions don’t have it. The only setup is the extension. If Claude says Chrome isn’t connected, install the Claude in Chrome extension from claude.ai/chrome in Chrome on that computer and sign in to the Claude side panel with the same Claude account and organization that computer’s Claude Code uses. Claude tells you which ones it uses; see Troubleshooting if it still can’t connect.@Bottari in channels and pages
When you mention @Bottari in a channel, or open Edit this page with Bottari on a page, a different assistant answers. On a page, its edits show as blue lines that you can revert, and only you see that chat. It runs on Bottari’s server, not on your computer, and it doesn’t use your Claude Code or your Claude subscription. In a session you talk to Claude directly, so @Bottari isn’t offered there.Where things run
- A session’s Claude runs on the runner’s computer under that person’s Claude subscription and goes straight to Anthropic. It doesn’t pass through Bottari’s server.
- @Bottari in channels and pages runs on Bottari’s server.
- Session records — messages, Claude’s replies, tool activity, the contents of files Claude read in the conversation, and attachments — are stored on Bottari’s server, and everyone with access to the session can see them. Your repository itself isn’t uploaded.
- A few app features send short excerpts through Bottari’s server to an AI model to write text for you: a session’s automatic title (a few hundred characters of the conversation), and commit messages, PR drafts and folder names (the code change, up to about 24 KB, plus a short conversation excerpt).