Skip to content

Pick your path

KAOS docs are organized the Diátaxis way — tutorials (learn), how-to guides (do a task), reference (look up facts), and explanation (understand). Different readers need different doors. Find yours.

You want proof, fast — no setup, no key.

  1. Run your first example — deterministic, ~10 seconds.
  2. Browse the gallery — pick any card, one uv run.
  3. How KAOS fits together — the 60-second mental model.

You want to learn KAOS properly, building as you go. Follow the golden path — each tutorial builds on the last, all runnable offline:

flowchart LR
    subgraph F["① Foundations"]
        direction TB
        t1["Your first tool"] --> t2["Build a document"]
    end
    subgraph L["② LLM programming"]
        direction TB
        t3["Offline FunctionClient"] --> t4["Your first model call"] --> t5["One-liner → program"]
    end
    subgraph A["③ Agents"]
        direction TB
        t6["Your first agent"] --> t7["Grounded citations"] --> t8["Research agent"]
    end
    subgraph C["④ Capstone"]
        t9["Build an app"]
    end
    F --> L --> A --> C

    classDef f fill:#eef2ff,stroke:#6366f1,color:#1e1b4b;
    classDef l fill:#f0f9ff,stroke:#0ea5e9,color:#0c4a6e;
    classDef a fill:#fef9c3,stroke:#ca8a04,color:#713f12;
    classDef c fill:#f0fdf4,stroke:#22c55e,color:#14532d;
    class t1,t2 f;
    class t3,t4,t5 l;
    class t6,t7,t8 a;
    class t9 c;
  1. Your first tool
  2. Build a document
  3. Offline LLM with FunctionClient
  4. Your first model call
  5. From a one-liner to a typed program
  6. Your first agent
  7. Grounded citations
  8. A research agent with citations
  9. Build an app (capstone)

You’re competent and want a recipe, not a lesson. The how-to cookbook covers tasks like:

You want exact API, CLI, tool, and setting details. The reference has the package map, CLI, MCP tools, environment variables, glossary, and more.

You want the why. Start with how KAOS fits together; the concepts section explains the agent loop, memory, retrieval choices, the cost-as-a-contract model, and grounded citations. The glossary cross-links every term.

You’re a contributor or module author. Start with your first tool and how KAOS fits together, then add your own app template, add typed settings, and adopt the offline-testing seam so your examples stay deterministic.

You want KAOS tools inside Claude Code, Codex, or another MCP client: connect an AI tool, serve a runtime over MCP, serve over HTTP with auth, and the MCP tools reference for what each package exposes.