OpenClaw Cookbook

Why it's ranked here

Its practical scope is unusually clear. Each recipe isolates one behavior, while the starters demonstrate how those behaviors fit into usable interfaces. A shared quality gate checks formatting, types, lint, tests, documentation, starter builds, and smoke runs. The main reservation is that the public SDK package is not yet available.

What's good

The examples teach operational details, not just prompt submission. They cover terminal events, timeouts, client cleanup, session continuity, cancellation, credentials, model selection, and protected Gateway connections. The command wrapper also redacts fields whose names suggest tokens, passwords, secrets, authorization data, or keys before printing results.

Tradeoffs

The repository currently depends on a private workspace shim because the public SDK package is still pending. That makes it useful for learning and validation, but weaker as a direct production dependency. Most connected recipes also require an OpenClaw Gateway and suitable credentials; only the in-memory transport example runs without one.

How to use it well

Use it when evaluating the SDK, learning one workflow at a time, or bootstrapping a terminal tool, control surface, or operations dashboard. Begin with the smallest matching recipe, run the full quality gate, then copy a standalone starter and replace the workspace dependency when the public package exists. It does not replace the Gateway or the SDK itself.

Observed

License

MIT

Primary language

TypeScript

Packaging

Private ESM package managed with pnpm; the SDK dependency is supplied through the workspace

Interfaces

Library-style recipes, command-line applications, and React web applications

Runtime

Node.js 22 or newer

Quality checks

The root gate covers formatting, typechecking, linting, Vitest, documentation validation, starter checks, and smoke runs