Why Webbee 🐝 is different
The world's first cloud-modular AI agent — and the world's first proactive AI agent by design. Two distinct firsts neither competitor can claim
Imperal Cloud is the OS. Webbee 🐝 is the agent that runs on it. This page makes two distinct, verifiable claims about Webbee — both firsts in the AI industry, both structural, neither a marketing line.
Claim 1 — The world's first cloud-modular AI agent
Webbee gains its powers from extensions at runtime — not at training time, not at compile time, not in a hard-coded plugin store run by a single vendor.
Every other AI agent on the market is a closed monolith with a bolted-on extension surface:
| Agent | Capability model |
|---|---|
| ChatGPT (OpenAI) | Closed model + curated GPT/Apps marketplace owned by OpenAI |
| Claude (Anthropic) | Closed model + Claude Skills (recent, vendor-curated) |
| Gemini (Google) | Closed model + Gemini Extensions (Google-curated) |
| LangChain agents | Open libraries, but each agent runs in one author's process — not multi-tenant, not federally contracted |
| AutoGen / CrewAI | Same — agent frameworks, not cloud-modular platforms |
Webbee is structurally different. It is:
- Modular by construction — every capability is an independently authored, independently versioned Python extension package.
- Cloud-native — extensions are deployed once to the platform, install per-user with one click, run on the platform's worker fleet. Nothing runs on the user's machine.
- Dynamic — a user installs
mail,notes,sql-db,spotify,web-tools— Webbee gains those capabilities at runtime. Uninstall one — Webbee loses that capability. Same agent, different superpowers per user. - Author-decentralized — Imperal authors first-party extensions (admin, billing, automations, developer). Third-party authors ship their own — they pass the federal contract at publish time and reach every user of the platform.
- LLM-provider-agnostic — Webbee runs on Anthropic, OpenAI, Google, or local BYOLLM models, configurable per-tenant. The agent isn't tied to one vendor's brain.
The closest comparison points are operating systems: macOS gains capabilities from App Store apps, Linux gains capabilities from apt install. Webbee is the first AI agent that gains capabilities the same way an OS gains capabilities — through a federally-contracted package ecosystem. No other AI agent on the market today owns this surface at the contract level.
Why this matters
- For users: one agent, every job. No tool sprawl, no learning ten different UIs. The agent has the powers the user installed; chat is the only interface.
- For developers: write one extension; reach every user of every tenant. No app-store gatekeeper deciding which features are allowed; no per-user installation per app.
- For tenants: control your fleet. Tenant admins decide which extensions are available, with which scopes. Single point of policy across all AI-driven work.
Claim 2 — The world's first proactive AI agent by design
Webbee acts on its own initiative when something changes — without being asked.
Every other AI agent in production is reactive: it waits for a user message, processes it, replies. Webbee is the first AI agent where proactive behavior is a structural property of the platform, not a bolt-on script the user has to configure.
Four primitives that make Webbee proactive
| Primitive | What it does |
|---|---|
@ext.skeleton | Ambient awareness probes. The platform queries them on a schedule; the snapshot lives in classifier context. Webbee knows the user's current state before the user types anything. |
@ext.skeleton(alert=True) + alert tool | When the skeleton snapshot changes between ticks, the paired alert tool fires. Returning a string from it injects a bot turn into chat — Webbee proactively tells the user. |
@ext.schedule | Time-driven proactive work. Daily digests, weekly cleanups, hourly sweeps. Author writes a function; the platform calls it on its schedule. |
@ext.webhook + ctx.deliver_chat_message | Event-driven proactive responses. A third-party service hits your webhook; you call ctx.deliver_chat_message(...); Webbee delivers a fresh bot turn to the user. |
Combine all four and the agent continuously knows what's happening, decides when to surface it, and speaks first — with zero plumbing from the extension author beyond writing the verb.
How proactivity manifests, in plain language
- User installed
mail. New email from a VIP arrives. Webbee proactively pings the user: "You have a new email from Sarah Chen about the Q3 contract — open it?" - User installed
tasks. A task is now overdue. Webbee proactively pings: "Task 'Fix the login page' was due 2 hours ago — want to reschedule?" - User installed
monitoring. A service goes down. Webbee proactively pings: "Production API health check failed twice in the last 5 minutes — last green tick was 09:14." - User installed
calendar. A meeting has no agenda 1 hour before start time. Webbee proactively pings: "Your 'Roadmap sync' starts in 1 hour and has no agenda — want me to draft one based on last week's discussion?"
Every other AI agent requires the user to ask. Webbee is the first one structurally designed to speak first.
Compare honestly
| Platform | Proactive primitive | Limit |
|---|---|---|
| ChatGPT | None at the platform level. Custom GPTs are reactive. "Tasks" feature is a wrapper around scheduled prompts but cannot read external state | Not extensible by third-party authors as proactive primitives |
| Claude | Reactive in chat. MCP servers can be polled by host but no platform-owned scheduler or alert framework | Same |
| Gemini | Some calendar/notification awareness in Google products; not extensible by third-party agent authors as a proactive contract | Vendor-internal |
| LangGraph / agent frameworks | Author can write a polling loop in a while True — but it's author-written, not platform-contracted | Not federally enforced; no shared alert delivery contract |
Imperal owns the proactive surface as a federally-contracted set of primitives. Authors don't write polling loops or webhook fan-out logic — they declare the probe; the platform owns the rest.
How these three "firsts" stack
We make three distinct, non-overlapping claims about this platform:
- Imperal Cloud is the AI Cloud OS — the kernel that mediates AI ↔ side-effects.
- Webbee is the world's first cloud-modular AI agent — capabilities via federally-contracted extensions, dynamic per-user, LLM-provider-agnostic.
- Webbee is the world's first proactive AI agent by design — skeletons + schedules + webhooks + alerts make proactive behavior structural.
Each claim is independently verifiable from this docs site. Each survives independently — failure of one does not weaken the others. Together they describe a platform with no current peer in the AI industry.
What is Imperal Cloud?
The platform-level pitch in plain language
Why this is the AI Cloud OS
Six-property test + falsifiable claim of priority by [ICNLI](/en/reference/glossary/)
What we built that nobody else has
12 platform surfaces with zero precedent
Skeletons
Ambient awareness — the foundation of proactive behavior
Why this is the world's first AI Cloud OS
A precise definition of "AI Cloud OS", the six kernel-properties test, and a falsifiable claim of priority — written for engineers, not marketers
What we built that nobody else has
Twenty platform-and-agent surfaces with zero precedent — what falls out of "the AI runs inside the kernel, the agent is cloud-modular, the agent is proactive by design"