# ox kb (https://sageox.ai/docs/cli/kb)

# ox kb

A Knowledge Bubble is a Curator-maintained, read-only synthesis of your team's distilled conversations for one area of work (see ox ADR-028). Team Contexts and Ledgers are separate, permanent conversation stores; they are not bubbles.

Use `ox kb list` to see the bubbles you can access and `ox kb describe <slug>` for details on one.

## Usage

<Terminal>
  <TerminalCommand>ox kb [command]</TerminalCommand>
</Terminal>

## Subcommands

| Command | Description |
|---------|-------------|
| `ox kb list` | List Knowledge Bubbles you can access |
| `ox kb describe <#slug\|kb_id>` | Describe a single Knowledge Bubble |

## Examples

<Terminal>
  <TerminalCommand>ox kb list --type=team</TerminalCommand>
</Terminal>

List the bubbles in this project's scopes, filtered to team-type bubbles. Inside an ox-initialized repo the ambient scope is the repo's team; personal-scope listing is deferred until personal-team provisioning rolls out.

<Terminal>
  <TerminalCommand>ox kb describe '#engineering'</TerminalCommand>
</Terminal>

Resolve a bubble by slug within the project's team and print its detail. The argument may be a `kb_id`, a slug, or a slug with the display `#` prefix; rename aliases are followed server-side.

<Terminal>
  <TerminalCommand>ox kb describe platform --scope team --json</TerminalCommand>
</Terminal>

Resolve `platform` in the named scope and emit scriptable JSON.

## Flags

| Flag | Description |
|------|-------------|
| `--type string` | (`ox kb list`) Filter by kb type: `personal`, `profile`, `team`, `repo`, or `custom` |
| `--scope string` | (`ox kb describe`) Scope to resolve a slug in: `team` or `personal` (personal is not yet available) |

## What's next

- [ox conversation](/docs/cli/conversation) - Browse the recorded conversations bubbles synthesize
- [ox distill](/docs/cli/distill) - The distillation that feeds a bubble's synthesis
- [Team Context](/docs/features/team-context) - The team-wide conversation store (not a bubble)