Memory
SuperLocalMemory
Governed, local-first memory for agents. Every recall points back to its source, and writers whose facts keep failing verification lose influence.
Bots · Claude Bot Bridge
Most setups that connect a chat bot to Claude Code put the bot in charge: you chat with the bot, and the bot hands the real work to Claude Code. Claude Bot Bridge does the reverse. Claude Code already holds your repository, your plan and your context, so it stays in charge and hands the bot the jobs a consumer bot does well, such as live web answers and longer tasks that run while you are away. There are two routes. For a quick question, a small signed helper drives the Muse desktop app through the macOS Accessibility API: it types one line into the chat you have open, checks the message box holds exactly that text before it presses Return, and reads the answer back. For a bigger job, Claude Code puts a card on a board you host on Cloudflare Workers, Docker or your own Mac; Muse reaches the board through a custom connector, claims the card, does the work and moves it to Done, and Claude reads the result. Version 0.1.0 supports Muse, verified on Muse 12.1 and 13.1. Grok, dots and more bots are planned.

Figures as reported by the project. Check them against the code and paper linked above.
See it run

Install
Grant Accessibility permission to the app that runs Claude Code (Terminal, iTerm, the Claude app or your IDE), then restart it. Keep Muse open on the chat you want to use and the Mac awake and unlocked. Run the board setup yourself, not through Claude: it prints your keys once. Give Muse the worker key only, never the owner key. Task text is processed by Meta's Muse service, and automating your Muse account may conflict with Meta's terms, so read them first.
Install the plugin (Mac, Node 20 or newer, Muse desktop app)
claude plugin marketplace add qualixar/claude-bot-bridgeclaude plugin install bot-bridge@claude-bot-bridge
Then, inside Claude Code
/bot-bridge:setupOptional: your own task board, run in your own terminal
cbb-board-init --cloudflareclaude plugin install bot-bridge-board@claude-bot-bridge
What it does
You work in Claude Code, and Claude Code decides what to hand to the bot. The bot never gives the orders.
For a quick question, the bridge types one line into the Muse chat you have open and reads the reply back into Claude Code. It never switches or creates chats.
For bigger jobs, Claude Code puts a card on a board you host. Muse claims it, posts progress, submits a result and moves it to Done; task_wait returns the moment it finishes.
It types only after the keyboard and mouse have been idle for 3 seconds, and if you start typing into Muse it clears the box and refuses.
Every message starts with [Claude Code], is one line of at most 500 characters, is checked in the box before Return and checked again after it lands. Nothing is pasted through the clipboard.
When Muse's controls are not where the rules expect, the helper types nothing and the task goes to the board instead.
What the helper looks for in Muse lives in a rules file signed with Ed25519 through an offline root key, so a Muse change is fixed without a new binary. Binaries are checked against a signed manifest and SHA-256.
Keys are stored as SHA-256 hashes and compared in constant time; task titles, briefs and results are encrypted at rest with AES-256-GCM.
One codebase: Cloudflare Workers with D1 (the free tier is enough), any Docker or Node host, or your own Mac behind a stable tunnel.
Use it for
Changelog
The latest releases on GitHub.
The first release of Claude Bot Bridge: Claude Code hands tasks to Meta's Muse, by direct chat on your Mac or through a task board you host yourself. Verified on Muse 12.1 and 13.1.