Concepts

bichito is small enough that you can hold its model in your head. This page is the cheat sheet.

Hive

Your top-level workspace. Owns the plan (Free or Pro), the owner (you), and any honeycombs under it. Most users have one hive; companies running unrelated products keep a hive per product so the inbox of one doesn't pollute the other.

Identified by a slug in URLs (/{hive-slug}/inbox).

Honeycomb

One project inside a hive. Each honeycomb has:

• A widget snippet with a project-scoped API key (sk_…).
• Its own bug inbox.
• Its own labels, blocklist, allowed origins and extra notification recipients.

A bichito always belongs to exactly one honeycomb.

Bichito

One bug report. The word is Spanish for "little bug" — we lean into it because "bug" is overloaded in software (insect / defect / Bugzilla).

Each bichito carries: a title and description, severity, status, optional assignee, labels, an optional reporter email/identifier, the URL it came from, the user-agent, the viewport, an optional image attachment, comments, and a full activity timeline.

Label

A colored tag scoped to one hive (so all your honeycombs in that hive share the same catalogue). Used for filtering and triage. Capped at no fixed number — practical limit is whatever fits in your inbox sidebar without scrolling.

Manage them in /{hive}/settings/labels or via MCP.

Saved view

A named combination of inbox filters (status / severity / assignee / honeycomb / labels / search) pinned to your /inbox. Per-user, per-hive — your saved views are private to you. Cap of 20 per (user, hive).

See Saved views.

API key (sk_…)

The publishable key the widget uses to POST reports. It only grants the right to ingest — it can't read the inbox, change settings, or touch other honeycombs. Lives in your end-user's HTML by design (see the transparency note in the widget docs).

Mint additional keys per honeycomb under Settings → Additional API keys; each can be revoked independently.

MCP token (mcp_…)

A per-user token that lets AI assistants (Claude Code / Cursor / others) act on your behalf via the MCP server. You pick the scopes at mint time — from "list my bichitos" to "create labels and update bug status".

Different concept entirely from the widget API key. The widget key is per-honeycomb and publishable; the MCP token is per-user and confidential.

JWT (Bearer token)

The session token your browser uses to talk to the dashboard. You don't usually see it; the login flow sets it for you. Lasts 30 days, refreshed on activity.

Activity timeline

Every mutation on a bichito (status change, severity change, assign, label add/remove, comment, mark spam, mark duplicate) leaves an activity row. The bug detail sidebar renders these as a timeline so you can see who did what when. Mutations made over MCP carry a via: "mcp" flag so the timeline distinguishes AI from human.

SSE stream

The dashboard subscribes to a per-hive Server-Sent Events stream and patches /inbox in real time when bichitos arrive or change. You don't configure it — it just works while a tab is open.

Public surface: GET /api/v1/teams/{hive_id}/stream?token=… — covered in API → Streams.