Local-first · Open Knowledge Format

Superbee turns what your agents know into infrastructure you can use.

Superbee is an OKF-compatible knowledge bundle of plain Markdown in your repo, plus a CLI built for agents. Superbee makes it easy for users and agents to define their own domain-relevant schema. The schema works like an API interface or contract, making information easier to discover, use, and extend.

Install Superbee
npm install -g superbee
EXAMPLE DOMAIN CONTRACT OKF BUNDLE
conventions/incident.md
---
type: Convention
governs: Incident
fields:
  required: [severity, service, state]
links:
  caused_by: Deployment
---
Declared structure gives agents a bounded, inspectable way to find and change work.
Local-first Plain markdown Structured for agents Open Knowledge Format
Start using Superbee immediately

You install one package.
Your agent helps you set it up.

  1. 01

    Install the CLI.

    npm install -g superbee

    (Requires Node.js 20 or newer.)

  2. 02

    Ask your agent to set up Superbee.

    Ask a Claude Code or Codex agent to run superbee setup. It reports the exact safe next command, one at a time, and does not change host configuration by itself.

  3. 03

    Restart once.

    After you apply the returned integration commands, restart the host. Later sessions can discover the workspace without being asked again.

Agent-first by design

Built for agents
to operate, not just observe.

Agents need more than files they can read. They need compact results, bounded paths to deeper context, and scoped changes whose outcomes are clear. Superbee is designed around those interactions.

01 / FIND

Get the relevant working set.

superbee list --type Incident --field state=open EXAMPLE RESULT
incidents/payment-timeouts   severity=critical   service=payments

Compact results identify the relevant records and links, so agents follow only the context the work requires.

02 / CHANGE

Change work against a declared model.

Scoped commands create or update records against declared fields and relationships, without reconstructing a human workflow.

03 / CONFIRM

Keep outcomes legible.

Writes carry attribution and version checks. A local View can show an exact before-and-after value for confirmation.

Generative Views

Ask your agent to create whatever view you need.

No dashboards to configure and no second system to keep in sync. Describe what you want to see and your agent will render it.

REQUEST TO AGENT

“Show open incidents grouped by service.”

KINDS FIELDS LINKS
EXAMPLE AGENT-AUTHORED VIEW EXAMPLE DATA
WORKSPACE / INCIDENTS

Open incidents by service

5 OPEN
PAYMENTS1
Payment timeouts CRITICAL
AUTH2
Token refresh loop HIGH
Expired invitation link MEDIUM
API2
Rate limit mismatch MEDIUM
Webhook retry gap LOW
PAYMENT TIMEOUTSCAUSED_BYDEPLOYMENT
How it compounds

Every session starts
further ahead.

Capability compounds when knowledge becomes infrastructure agents can discover, reuse, and extend, with interfaces that turn domain understanding into repeatable action.

  1. 01

    Model the domain

    Start with the concepts, constraints, and language your work already uses.

  2. 02

    Make it operative

    Define kinds, fields, and typed relationships. Agents can author Views and reusable project conventions against that model.

  3. 03

    Build together

    People and agents read, contribute, and operate from the same evolving model.