Weavecrew updates itself — it checks on launch and every six hours, downloads in the background and installs the next time you quit. Nothing restarts mid-job.
Connect a bot token and one of your teammates becomes reachable from your phone. A message runs a real turn — same persona, same memory, same approval rules — and the answer goes back to the chat. It keeps working with the window closed, and reconnects by itself if the connection drops.
Every channel has an allow list that starts empty, and an empty list means nobody — never everybody. A stranger who messages the bot gets no reply and no hint that it exists; they show up in the app instead, where one click lets them in. In servers and groups the bot only answers when mentioned, and it never starts a conversation or messages anyone you haven't approved.
Downloads and updates now come from the real domain over its own certificate. The old address keeps working, so copies installed before this update carry on updating normally — nothing to reinstall.
A new tab lists every MCP server and every Claude Code plugin available on this machine, read live from the CLI itself. Real connection status per server — connected, needs auth, or the actual failure reason — plus the full config behind each one, a plugin's component inventory and its token cost, and an enable/disable switch. It also shows what Weavecrew adds on top that the CLI can't see.
Weavecrew held its whole state in memory and wrote it back wholesale, so when a bot added a new teammate by editing the state file, the next save silently erased it. Outside edits are now picked up live — the new bot appears in the rail within seconds, without a restart, and survives.
Renamed from Claude Bot. A rename moves where the app stores its data, so a copy installed under the old name sits alongside this one rather than upgrading into it.
Give one bot a coordinating role and it hands work to the right teammate itself. The delegated job opens as a real conversation on that teammate and streams live — its own persona, its own memory, the same approval gate.
Chat only, ask before anything risky, auto-approve but stop on dangerous actions, or never ask. The status bar turns red when a bot is running unguarded.
Point a bot at a different backend, drag files or paste images straight into a conversation, and let the app keep itself current — updates arrive as a small differential download rather than the whole installer.
Persistent bots with their own memory, the shared computer with its live activity feed and terminal, skills, routines on an English schedule, and the approval gate that intercepts every tool call.