Start here

kaboo is three libraries that snap together. Pick the path that matches what you want to build — you can always add the others later.

flowchart TD
    Q{What do you want?}
    Q -->|Orchestrate agents| WF
    Q -->|Persist & replay runs| RT
    Q -->|Render agent activity| RC
    Q -->|The whole thing| FS
    WF[kaboo-workflows]
    RT[kaboo-runtime]
    RC[kaboo-react]
    FS[Full-stack tutorial]

I want to orchestrate agents

Define models, agents, tools, MCP servers, and multi-agent orchestrations (delegate / swarm / graph / parallel / nested) in YAML, then serve them as an AG-UI SSE endpoint. load() returns plain strands objects, so you can also drive agents in-process. Host backends get a first-class per-run side channel (forwardedProps → get_forwarded_props()), authorized attachment fetching (attachments.base_url / authorization), and — with create_agui_app(session_config_key=...) — runs that submit their own config, so one process serves many workflows and editing one takes effect on the next turn without a restart.

→ kaboo-workflows · Getting started

I want to persist and replay runs

Drop a plugin into a CopilotKit runtime (NestJS or any Node framework) that records the full event log per thread and replays it on reconnect — so a browser refresh mid-run or post-run restores exactly what happened. Ships an InMemoryThreadStore and a PostgresThreadStore, and records real thread ownership (accessPolicy.ownerOf → createdById) so hosts can scope thread lists per caller without parsing ids. Persisted state is replayed into the next run, which is what makes conversation history server-owned and a pending human-in-the-loop approval durable across a restart.

→ kaboo-runtime · Concepts

I want to render agent activity

Drop-in React components + hooks that turn the AG-UI run stream into a live, hierarchical activity tree with drill-down and human-in-the-loop, inside a CopilotKit chat.

→ kaboo-react · Concepts

I want the whole stack

Wire all three end-to-end: YAML agents → served over AG-UI → persisted in a CopilotKit runtime → rendered in React, backed by Postgres.

→ Full-stack tutorial

How they fit together

flowchart LR
    C[kaboo-react<br/>UI] -->|/api/copilotkit| R[kaboo-runtime<br/>CopilotKit runtime]
    R -->|HttpAgent| W[kaboo-workflows<br/>AG-UI SSE]
    R <-->|persist / replay| DB[(Postgres)]
    W -->|AG-UI events| R
    R -->|streamed events| C