A team of AI bots on your computer.
Give them work, connect your tools, and keep chatting from your phone.
Download Beans · Try the demo · Read the docs · Compare alternatives
Beans gives each bot a name, instructions, a model, and memory. Assign it to one of your computers and give it a folder to work in. Chat with it directly, or bring several bots into a group to work together.
|
Keep dedicated bots for different projects. Their instructions and memory carry across chats, so you can return to the work without repeating your preferences. |
Put up to six bots in a group. Mention a teammate, discuss the work together, and let bots hand tasks to each other. |
|
Bots read and edit files, run commands, search the web, and connect to apps through MCP plugins. Review tool permissions and see the activity in the conversation. |
Pair your devices to read and send messages, configure bots, and start work remotely. Scheduled routines run on the bot's assigned computer. |
The interactive demo uses the actual Windows/Linux app interface. Select bots and group chats in its sidebar. It contains sample conversations and simulated replies; providers, files, and tools are disconnected.
- Download Beans for your computer. The download page shows the currently available builds.
- Connect an AI provider with a supported subscription sign-in or API key.
- Create a bot, choose its model, and assign its computer and working folder.
- Start a conversation. Add teammates, scheduled routines, and paired devices when you need them.
Keep the assigned computer online for new turns and scheduled work. Your phone sends work to that computer; queued work waits while it is offline.
Beans is free and open source. You pay your AI provider directly for its subscription or API usage. Your computer, hosting, and any paid tools have their own costs.
Supported connections include:
- ChatGPT through subscription sign-in. Production Grok subscription OAuth is disabled pending a verified Beans OAuth/referrer contract; Grok models via API-key gateways remain separate.
- Anthropic, DeepSeek, OpenCode Zen, and OpenCode Go through API keys.
- Custom providers with OpenAI-compatible or Anthropic-compatible APIs, including reachable local model servers that implement a supported API.
Choose a provider and model for each bot. Provider availability and usage limits depend on your account. See provider setup and the provider architecture for connection details.
A desktop computer is a Runner. It runs the bots assigned to it and calls your model providers. A paired phone or tablet is a Device that lets you chat and manage the team.
flowchart LR
Desktop["Desktop app"] <-->|"Local connection"| Runner["Runner · Rust CLI"]
Runner <-->|"Encrypted sync"| Relay["Relay"]
Phone["Paired phone or tablet"] <-->|"Encrypted sync"| Relay
Runner -->|"Prompts and tool results"| Provider["Your AI provider"]
Runner --> Tools["Files · commands · MCP tools"]
Identity starts with a local key pair. Paired devices share chats, bot profiles, and account provider credentials through an end-to-end encrypted relay. The relay stores public keys and ciphertext and sees connection metadata such as sizes and timing. Your chosen model provider receives the prompts and tool results sent to it.
Bots run tools with your operating-system user's permissions. A working folder supplies context; it is not a filesystem sandbox. Auto-review evaluates tool requests and does not provide an operating-system sandbox. Read the identity and tools docs for the boundaries.
Each comparison has its own page with pros, cons, costs, and source links:
OpenClaw · Hermes Agent · Grok Bot · OpenAI Dots · OpenBot · Claude Code
The website is available in English, Português do Brasil, 简体中文, Deutsch, Español, and 日本語. Product docs are available in English and Chinese. Website translations are separate from native app language support.
Read ARCHITECTURE.md before changing code, then the subject docs it lists for the parts you touch. The binary is beans, configuration uses BEANS_*, and pairing uses exact beans://pair?v=2&… links.
Install Node 24.22.2, pnpm 12.18.0 and Rust stable. macOS builds need Xcode with Swift 6 and the macOS 26 SDK. Windows/Linux desktop builds need Go 1.27.1 or newer and the host webview dependencies. Phone builds need Xcode for iOS, or JDK 17 and the Android SDK/NDK for Android. See the macOS, desktop, and phone build docs.
git clone https://github.com/bloodf/beans.git
cd beans
# To reproduce a release, check out its beans-v<version> tag before installing.
pnpm installChoose the command for your platform:
pnpm run dev # Build and launch Beans Dev on macOS, with a local relay
pnpm run build # Build Beans.app
pnpm run desktop # Windows/Linux development app with live reload
pnpm run desktop:build # Build the desktop release artifacts
pnpm run mobile:dev # iOS simulator development with Metro
pnpm run mobile:phone # Development on a connected iPhone
pnpm run android # Rebuild the Rust phone core and run the Android client
pnpm run web # Website development on localhost:3000For phone development, first run pnpm --dir mobile install. The phone app is not a root pnpm workspace. Desktop cross-compilation uses cargo-zigbuild; platform prerequisites and packaging details are in the build docs above.
Beans uses ~/.beans-v2 and CLI port 4874; Beans Dev uses ~/.beans-dev-v2 and 4875. Phone cores use beans-v2/core or beans-dev-v2/core inside the existing OS sandbox. Format beans-v2, protocol 5 and versioned backups are intentionally incompatible with old accounts, unversioned phrases and mixed paired Devices. No migration/reset occurs; existing accounts, installed apps and services remain untouched. To run the development CLI directly:
cargo run -q -p beans -- --home "$HOME/.beans-dev-v2" --port 4875 servepnpm run dev starts its local relay on every network interface so phones can pair. Use a trusted network. pnpm run reset deletes local installation data; it is not a setup prerequisite.
New backup phrases start with the separate token beans-v2, followed by thirteen base32 groups. Restore rejects missing/wrong prefixes before decoding. Do not reuse or reset an existing account directory to make a fresh build start. Relay account requests carry Beans-Protocol: 5 and Beans-Format: beans-v2; incompatible storage and peers fail closed.
A relay enables pairing and sync across devices. Run a local instance with:
cargo run -q -p beans-relay -- --bind 127.0.0.1:8787 --db beans-relay.dbSet BEANS_RELAY_SECRET to a stable random value so devices remain authenticated across restarts. Configure clients through BEANS_RELAY_URL or Settings > Advanced; no production relay is guessed. .env.example documents push settings. Keep credentials and signing keys outside the repository.
The relay supports SQLite or Postgres and has a container recipe. Follow the relay and protocol docs for deployment, proxy configuration, and compatible client upgrades.
| Directory | Contents |
|---|---|
crates/ |
Rust CLI, agent runtime, providers, model catalog, relay, and phone core |
macos/ |
AppKit macOS app |
desktop/ |
Go and Solid Windows/Linux app |
mobile/ |
Expo phone app |
web/ |
Marketing website and product docs |
design/brand/ |
Editable SVG logo masters, campaign artwork, and brand exports |
packages/beans-blobatar/ |
Offline avatar generator |
docs/architecture/ |
Architecture subject docs |
Beans releases use signed readiness metadata. macOS release bundles check the Beans Sparkle feed for updates; development builds do not start update checks. Build validation, signed artifact publication, and store submission are separate steps described in releases.
Keep changes focused on an observable behavior. Exercise the path with an isolated home and local fixtures, update the architecture subject for any mechanism you change, and record the change in CHANGELOG.md.
Run the checks relevant to your change:
cargo test --locked --workspace --exclude beans-mobile
cargo test --locked -p beans-mobile # Separate to avoid Runner feature unification
pnpm run check:docs
pnpm run l10n
pnpm run test:mac-startup
swift test --package-path macos
pnpm --dir mobile typecheck
pnpm --dir mobile test
pnpm --dir desktop build:web
pnpm --dir desktop test
go -C desktop test ./...CI also checks Linux/Postgres and Windows. Report the commands you ran and any unavailable prerequisites. Native UI, pairing, and deployed services need their own verification.
Beans is licensed under MIT and builds on Lorca by egoist, preserving its source history and required attribution. The vendored Blobatar avatar source by Alain is MIT-licensed.
The read-only tracked-name check takes the provenance name explicitly: pnpm run scripts/check-tracked-names.ts Lorca. It inspects tracked paths/content, allows provenance only here and preserves its enumerated required legal notices; run it after tracked path moves are reconciled.
Website · Downloads · Documentation · Releases · Privacy · Support
