Concepts Overview

These concepts describe how Meerkat runs agents from the CLI, inside an application or as part of an ongoing system. Start with sessions, models and tools; add memory, schedules and multi-agent coordination as your work needs them. The CLI, services, SDKs and browser runtime share the same lifecycle and capability contracts. The central idea is a realm: the identity and storage boundary within which config, credentials, sessions, schedules, WorkGraph commitments, jobs, blobs, artifacts, and mobs can coordinate.

Core Read Order

Composability explains why the surfaces share contracts instead of implementing separate agent loops.
Realms defines state identity, isolation, storage discovery, and backend pinning.
Sessions covers transcript, lifecycle, history, concurrency, persistence, and recovery.
Configuration covers raw realm documents, effective inheritance, runtime overrides, and generation CAS.
Auth and bindings separates model/backend choice from credentials and account identity.
Providers explains the model catalog, capability gating, provider parameters, and fallback.
Tools explains how an agent acts on the world.

Then add the systems your product needs:

Ownership At A Glance

Concept	Main question
Composability	Which capabilities should this product assemble, and through which surface?
Realms	What state is shared, where is it stored, and what stays isolated?
Sessions	How does one agent conversation execute, persist, resume, and end?
Configuration	Which settings are raw, inherited, or overridden for one request?
Auth and bindings	Which backend, account, and credential source serves this model call?
Providers	Which model owns an ID, and what can it do?
Tools	Which actions are visible and authorized for this session or turn?
Memory and compaction	How does useful context outlive one request window?
Comms and mobs	How do session-backed agents coordinate as a team?
Scheduling and jobs	How does timed or detached work run durably outside an immediate user turn?
WorkGraph	How are durable goals, commitments, evidence, and attention tracked?
Live channels	How does realtime audio/text transport attach to session identity?

Choose A Build Path

Goal	Start with
Embed Meerkat in Rust	Rust SDK overview
Build in Python or TypeScript	Python SDK or TypeScript SDK
Run a browser/WASM agent	Web/WASM example
Host Meerkat as a service	JSON-RPC or REST
Build a coordinated team	Mobs guide
Run detached work	Durable jobs and monitors
Run private models	Self-hosting models
Study ownership and internals	Architecture

Getting started

Concepts

Guides: Models And Hosting

Guides: Runtime Behavior

Guides: Orchestration

Examples: Foundations

Examples: Capabilities

Examples: Orchestration And Deployment

Concepts Overview

Core Read Order

Ownership At A Glance

Choose A Build Path

See Also

​Core Read Order

​Ownership At A Glance

​Choose A Build Path

​See Also

Core Read Order

Ownership At A Glance

Choose A Build Path

See Also