OpenBot hits 3,500 GitHub stars: here's what's new in v0.0.5!

OpenBot just crossed 3,500 stars on GitHub 🎉 — and the v0.0.5 release includes many requested features. OpenBot turns agents from clever assistants into coworkers you can actually trust with real work: they can pull from your team's knowledge, hand off to each other, run on a schedule, and get deployed onto real infrastructure.

Quick resources:

• GitHub: github.com/CopilotKit/openbot
• Docs: openbot docs

Here's what we added...

1. New first-party connectors: Google Drive and Notion

Two new first-party connectors ship in v0.0.5. Each person connects their own account, so a Bot only ever sees what that person is allowed to see — and answers come from the live files with a link, not a stored copy. Notion supports both reading and writing; Drive is read-only for now.

2. Bot-to-bot delegation

A Bot asked something outside its wheelhouse can now hand the question to the right Bot, which answers as itself with its own tools and knowledge. If no Bot can help, it reaches out to a person instead. Admins control exactly which Bot may ask which — nothing is delegated until someone turns it on.

3. Routines: scheduled Bots

You can now tell a Bot "every weekday at nine, post the standup notes here" and it just happens. A routine runs with its creator's permissions (it can do exactly what they could do in chat, nothing more), replies in the channel like a normal message, and switches itself off with a notice if it keeps failing.

4. Smart message routing

No more chasing the right @-mention. An untagged message is automatically sent to the coworker whose purpose best matches it, and the choice (and the reason for it) is recorded. @-mentioning still wins when you want a specific Bot.

5. "Take the wheel"

A person can now grab live control of a Bot's browser at any point — for example, to get past a sign-in page — and the Bot fully pauses while a human is driving. You no longer have to wait for the Bot to ask.

6. Smarter tool use via skills

Bots with lots of connected tools now get offered only the tools relevant to the message at hand, which makes them much more reliable at picking the right one. Skills — reusable instructions bundled with their tools — can be authored in the product or shipped with a deployment package, including per-coworker.

7. Ship it: enterprise sign-in and Kubernetes

• Enterprise SSO with Google, Microsoft, and Okta, plus real admin controls over who gets in.
• Helm chart for Kubernetes, proven on a real AWS cluster. Each Bot gets its own isolated computer that suspends when idle (keeping its logins) to keep costs down. Works on EKS, GKE, AKS, or your own cluster.

8. Safer by default

• Test a rule before saving it — admins writing boundary rules (what Bots may and may not do) can dry-run them against past activity to see what would have been blocked.
• Security hardening across the board — Bots can't be redirected to internal or cloud metadata addresses, credentials are locked to the service they belong to, the database is off the Bots' network, and every refusal and failure lands on the audit trail.

9. And a lot of polish

Pin and delete channels, unread dots on channels a Bot has spoken in, conversations that recover on their own instead of dying, support for the newest reasoning models (with a "how hard to think" setting), and no more white flash on refresh.

Get started

OpenBot is open source and self-hostable. Grab the latest release, kick the tires, and tell us what to build next.

• GitHub: github.com/CopilotKit/openbot
• Docs: openbot docs

Star us if OpenBot is useful — and if you're running it in production, we'd love to hear about it.

Want to bring CopilotKit into your stack? Talk to our engineers and we'll help you set it up.

Follow CopilotKit on Twitter for updates. If you get stuck, reach out in the CopilotKit or AG-UI communities.