Live means shipped
A product route, client, or protocol exists today.
Complete product catalog
Chat, research, create, build, integrate, govern, and run specialist compute from one system. This catalog separates live product capability from previews, customer-scoped deployments, and work still in progress.
Catalog reviewed 2026-09-28 · machine-readable JSON
A product route, client, or protocol exists today.
Model, plan, provider, and distribution limits are stated beside the feature.
Model, pricing, docs, TrustHub, and roadmap pages carry the supporting detail.
Showing 35 capabilities
Ways to communicate with Bee and work across media.
Streamed conversations with text, images, audio, video, and documents.
Input support varies by model tier.
Prompt-to-image generation in the Bee workspace with retained conversation assets.
Plan allowances and provider capacity apply.
Analyse uploaded images and, on eligible tiers, video input.
The model matrix identifies the eligible tiers.
Speech transcription, voice mode, and spoken responses across supported clients.
Speech is delivered through configured external inference providers.
Asynchronous prompt-to-video generation with persisted job and asset handling.
Built but not advertised as generally available until production completion evidence passes.
Ground answers in current sources and private working context.
Fresh web grounding with source links for time-sensitive questions.
Shown only when a search provider is healthy on the active deployment.
Multi-source research synthesis with citations and an explicit research workflow.
Requires the live-search path.
Upload, extract, chunk, embed, retrieve, and cite tenant-scoped source passages.
User-controlled remembered context with search, review, and deletion controls.
Organise work, preserve instructions and resources, and search conversation history.
Native long-context models plus dedicated one-million-token modes on eligible tiers.
Context limits are model- and plan-specific.
Turn responses into reusable work and controlled actions.
Extract, preview, copy, download, and reopen generated code, HTML, and documents.
Create recurring or one-time Bee work with run history and delivery controls.
Structured tool calls for agent and application workflows.
Available on the tiers marked in the model matrix.
Schema-constrained JSON responses on eligible production models.
Available on Comb, Buzz, and Hive.
Approval-gated repository reading, editing, command execution, and evidence collection.
Execution occurs on the user's trusted device or workspace.
A capability-declared host protocol with action-level approval requirements.
Host validation exists; it is not presented as unrestricted autonomous control.
Use Bee from code, agents, editors, and connected tools.
Chat Completions-compatible requests, streaming, models, tools, and multimodal inputs.
Published client libraries for typed application integration.
Hosted OAuth, local stdio, and loopback transports for Bee tools and context.
Bee Code for VS Code, Cursor, VSCodium, and compatible editors.
Connect Cursor, Windsurf, Continue, Zed, JetBrains, Aider, and compatible clients.
Support depends on each client's OpenAI or MCP compatibility.
Bring public repository content into an authorised Bee Code or workspace flow.
Use Bee across devices and organisational boundaries.
The complete hosted Bee experience in a modern browser.
Signed mobile access with native OAuth handoff, device controls, and push support.
Native iOS client sharing the governed Bee workspace surface.
Distribution status is reported on the download page.
Native Bee shells for macOS, Windows, and Linux.
Signed-release status is reported per platform.
Membership, seats, pooled usage, plan controls, and organisation administration.
Ephemeral conversations, history choices, export, retention, and account deletion controls.
Governed operation, security evidence, and specialist compute paths.
Plan-aware usage reporting, scoped API keys, credit controls, and account administration.
Release controls, public model lineage, operational status, and security boundaries.
NIST-standardized post-quantum signatures and integrity evidence for governed records.
Public service transport remains TLS 1.3; PQ transport is customer-scoped.
Explicit, metered quantum-reasoning jobs with provider, budget, receipt, and result records.
Never implied for ordinary chat; provider and spend approval are explicit.
Contract-defined tenancy, key control, network, locality, and operating boundaries.
Rights-aware research, specialist knowledge packs, tools, policy, evaluations, and corrections.
The control plane exists; the complete runtime is not represented as released.
Use Bee in the browser or choose the API, SDK, MCP, mobile, desktop, and editor surface that fits your workflow.