Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
The agent-native OS for companies.
| Date | Stars |
|---|---|
| 2026-07-31 | 386 |
| 2026-08-06 | 386 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
15.0
growth rate 0.00%/day
<div align="center">
# Beevibe
### The agent-native operating system for companies.
[](./LICENSE)
[](https://github.com/beevibe-ai/beevibe)
[Architecture](#architecture) · [Concepts](#core-concepts) · [Quick Start](#quick-start) · [Deploy](./DEPLOYMENT.md) · [Contributing](./CONTRIBUTING.md)
</div>
---
## What is Beevibe?
Beevibe is a shared workspace where a team's people and AI agents work side
by side. Agents hold lasting roles, build bounded domain memory, ask the
right teammate when their context runs out, and escalate blockers back to
humans.
It's the missing layer between your AI tools and your team. Slack, Notion,
and Linear are how humans coordinate. Beevibe is the same surface for the
AI side of the team — so the same context isn't re-explained dozens of
times a week and the same answer isn't learned and forgotten across
different engineers.
Beevibe is **self-hosted**. You own the Postgres database, the Node
services, the local daemon processes, and the CLI binaries doing the work.
## Why Beevibe?
Every engineer now works with AI all day: Claude Code, Cursor, Codex, and
whatever comes next. Individually, they're faster than ever. Then the team
gets in a room together and coordination is still stuck at 2019 speed.
The problem isn't that the agents are too weak. The problem is that each
person's AI work lives in a private bubble, and no shared intelligence
compounds.
- **Shared AI workspace.** People and agents work in the same team graph
with tasks, ownership, review, handoffs, and escalation.
- **Persistent specialists.** Each agent has an identity, domain, hierarchy
level, and bounded memory that deepens across sessions.
- **Agent-to-agent coordination.** When an agent leaves its domain, it can
ask another specialist for context or negotiate toward a solution.
- **Human-in-the-loop control.** Humans review, redirect, revise, cancel,
and resolve blockers from the dashboard.
- **BYO CLI.** Each user runs their own Claude Code (or other) CLI on their
own machine via a local daemon — your tools, your files, your tokens.
## Architecture
```text
Humans Agents
────── ──────
┌──────────────────────────┐ ┌──────────────────────────┐
│ Web dashboard │ │ Claude Code CLI │
│ (Next.js) │ │ (one per agent run) │
└────────────┬─────────────┘ └────────────┬─────────────┘
│ REST + SSE │ MCP tools
│ │ (HTTPS)
▼ ▼
┌─────────────────────────────────────────────────┐
│ @beevibe/api │
│ control plane: REST · SSE · MCP · /runtime · WSS │
└─────────┬─────────────────────────┬─────────────┘
│ │
│ SQL │ WS push +
│ │ HTTP claim
▼ ▼
┌──────────────────────┐ ┌─────────────────────┐
│ Postgres + pgvector │ │ beevibe-daemon │
│ shared state, mesh, │ │ (your laptop) │
│ memory, sessions │ │ │
└──────────┬───────────┘ │ spawns the local │
│ poll for │ Claude CLI for │
│ fallback claim │ every session │
▼ │ pinned to this │
┌──────────────────────┐ │ machine │
│ @beevibe/scheduler │ └─────────────────────┘
│ server-side spawn │
│ (offline daemons) │
│ + orphan reaping │
└────Excerpt of 8,549 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:12a8b1298ffdc685, topic:multi-agent-systems