by Bitterbot-AI
Bitterbot - a mesh of agents that turns shared experience into collective capability.
# Add to your Claude Code skills
git clone https://github.com/Bitterbot-AI/bitterbot-desktopGuides for using ai agents skills like bitterbot-desktop.
Last scanned: 4/29/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-04-29T06:25:29.001Z",
"semgrepRan": false,
"npmAuditRan": false,
"pipAuditRan": true
}See how bitterbot-desktop compares with popular alternatives.
bitterbot-desktop is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Bitterbot-AI. Bitterbot - a mesh of agents that turns shared experience into collective capability. It has 2,480 GitHub stars.
Yes. bitterbot-desktop passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/Bitterbot-AI/bitterbot-desktop" and add it to your Claude Code skills directory (see the Installation section above).
bitterbot-desktop is primarily written in TypeScript. It is open-source under Bitterbot-AI on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh bitterbot-desktop against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Build a history with your AI. Keep what it learns.
Bitterbot runs on your machine, remembers context across conversations, and works through a real browser, code execution, and the chat apps you already use. Give it a project, return with a new decision, and continue with the context it has retained.
Between conversations, it dreams: consolidating memories, preparing grounded briefs, and feeding a learning pipeline that proposes and tests reusable skills. Through Circles, you can connect with people you know and their independently owned agents.
Your agent's memory, identity, and skills live in files and SQLite on your disk. Inspect them. Back them up. Choose a different supported model. Modify the code. The history you build stays under your control.
Meta's Muse and OpenAI's dots made the persistent personal agent mainstream: an AI that remembers you and keeps working after you close the app. Bitterbot is the same idea, built to be yours. It runs on your machine, its memory is plain files you can read and correct, you choose the model, and it's MIT-licensed.
Start with a task you already do. These are example requests to try after configuring the relevant tools and channels:
| Bring it into your day | Try asking |
|---|---|
| Research with context | “Compare these three services against the requirements we discussed. Save the sources and flag what you couldn't verify.” |
| Work on real files | “Read this CSV, check the totals, and write a report explaining the discrepancies.” |
| Pick up a project | “What did we decide last time, what's still open, and what should I work on next?” |
| Prepare recurring work | “Every Friday at 4 PM in my timezone, summarize this project's open tasks and send me the report on Telegram.” |
Talk through the Control UI, WhatsApp, Telegram, Discord, Signal, Slack, or email. Browser automation, code tools, scheduled jobs, and durable tasks give the agent ways to act on those conversations. Background work runs while the gateway is running.
Explore the tools · Connect a chat app · Long-horizon tasks
One command. Paste it into a terminal on macOS (Apple silicon or Intel) or Linux (x64/arm64) and it takes you straight into setup:
curl -fsSL https://github.com/Bitterbot-AI/bitterbot-desktop/releases/latest/download/install.sh | bash
It downloads a signed release with its own Node runtime (no Node, no sudo, nothing else to install), verifies it, and runs the setup wizard, which asks for a model key, offers web search, and opens the Control UI at http://127.0.0.1:19001. What it verifies, and how to pin, roll back, or remove: install script guide.
Windows: open PowerShell (not Ubuntu/WSL) and run this. It installs inside WSL2 for you (no administrator rights needed once WSL2 is set up):
irm https://raw.githubusercontent.com/Bitterbot-AI/bitterbot-desktop/main/scripts/install.ps1 | iex
Already in an Ubuntu/WSL terminal? Use the macOS/Linux line instead, and run it from your Linux home (cd ~), not from /mnt/c.
Server (Docker). The compose file is attached to every release:
mkdir bitterbot && cd bitterbot
curl -fsSLO https://github.com/Bitterbot-AI/bitterbot-desktop/releases/latest/download/docker-compose.yml
docker compose up -d
Get the gateway token with docker compose exec -u node bitterbot-gateway node bitterbot.mjs config get gateway.auth.token (or use your BITTERBOT_GATEWAY_TOKEN), then open http://127.0.0.1:19001. Fly.io and VPS templates: Docker guide.
Already manage Node with nvm, fnm, Volta or Homebrew? Then npm install -g bitterbot && bitterbot onboard works too (Node 18 or newer); the package is a small launcher that downloads the same signed release on first run. Never run it with sudo. With Node from nodejs.org or from apt, npm cannot write to its global folder and fails with EACCES; the fix is the one command above, not sudo. Details: npm package.
Developing Bitterbot. Install from source with pnpm, below.
Make your first conversation personal:
“I'm working on [project]. My priorities are [priorities], and I prefer [communication style]. Remember this, then help me plan the next step.”
Later, start a fresh conversation and ask what it remembers about the project.
| Installed with | Update |
|---|---|
| Installer | bitterbot update, or rerun the installer: it switches a running older Bitterbot to the new version for you |
| npm | bitterbot update (updates the app in place), or npm install -g bitterbot@latest |
| Docker | docker compose pull && docker compose up -d |
| Source | pnpm bitterbot update in the checkout |
Your memory, settings, and keys live in ~/.bitterbot and are kept across updates. The Control UI tells you when a new release is out. Updating and rolling back
Node 22.12 or newer and pnpm. On Windows, use WSL2 and clone into the Linux filesystem (~/bitterbot-desktop), not /mnt/c/...: the Windows mount makes startup dramatically slower.
corepack enable pnpm || npm install -g pnpm
git clone https://github.com/Bitterbot-AI/bitterbot-desktop.git
cd bitterbot-desktop
bash scripts/setup-deps.sh # system packages; may ask for sudo
pnpm install
pnpm exec playwright install --with-deps chromium # browser automation
pnpm bitterbot onboard
Start it again later with pnpm start:all (it builds anything missing on first run). For development with hot reload:
pnpm dev:all
If no prebuilt P2P orchestrator exists for your platform, build it with a Rust toolchain: cargo build --release --manifest-path orchestrator/Cargo.toml.
The gateway serves the Control UI and hands it the auth token over loopback, so opening http://127.0.0.1:19001 on the machine that runs it just works. From another machine, forward the port:
ssh -N -L 19001:127.0.0.1:19001 user@host
Then open http://127.0.0.1:19001 locally. The first-run screen also accepts a remote gateway URL and its token (gateway.auth.token in ~/.bitterbot/bitterbot.json).
Talk to your agent from the terminal:
bitterbot agent --agent main --message "What have you learned about me so far?"
Prefe