> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rkat.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Meerkat Meta

> Compose Core agents into applications with memory, routing, policy, approvals and an operator console.

*Mirrored from Meerkat Meta main at [26f5ae9da1fd](https://github.com/lukacf/meerkat/commit/26f5ae9da1fd3caac378f1cd847ce50f9ec5ac92) on 2026-11-03; Meta version 0.9.9 at that commit.*

Meerkat Meta is the application layer around Meerkat Core. It brings lasting
agent identities, memory, routing, access policy, approvals and a console into
one composition. Use it when agents need an operational home and a way for
people and other systems to work with them over time.

Core already runs agents and multi-agent mobs. Meta adds the application
composition and operating experience on top of those runtime contracts.
It does not require Meerkat Connect.

> [card] [Start a runtime](https://docs.rkat.ai/meta/quickstart.md)
>
> Connect an SDK, configure the application and open its console.

> [card] [Choose your starting point](https://docs.rkat.ai/introduction.md)
>
> Compare Core, Meta and optional integration setup.

## From a personal agent to a working organization

An application can combine personal agents, domain specialists and coordinators
with temporary workers. Profiles describe capabilities. A roster describes the
lasting identities you want to keep available. Topology describes who can
communicate. Core executes and coordinates the agents; Meta packages the
application's desired state, persistence providers and operational interfaces.

An agent's stable identity remains its address when its runtime binding changes.
Use this for enduring roles. Short-lived workers need not become a permanent
population of identities.

## What you get

| Area | Purpose |
| - | - |
| Memory | Records with provenance and trust, bounded recall, optional distillation and background consolidation |
| Policy | Authenticated access, attribute-based view/steer rules and application-defined approval decisions |
| Operations | Routing, delivery, health supervision and persistent application state |
| Console | Conversations, roster, topology, shared work, memory, approvals and timeline inspection |
| Integration surfaces | Rust composition, JSON-RPC, REST, SSE and Python/TypeScript SDKs |

Memory is an agent capability, not just another chat history. Its
[record and retrieval system](https://docs.rkat.ai/meta/concepts/memory.md) can preserve useful experience,
keep untrusted writes separate and select what belongs in the next context.
Applications choose their providers and policy.

The console is a view of the same system the SDKs operate. Its projections do
not replace Core's session, mob or lifecycle state. See the
[unified runtime guide](https://docs.rkat.ai/meta/guides/unified-runtime.md) for the composition boundary.

## Add only what your application needs

Use your own tools and integrations, or add **Connect** for agent-led setup.
Connect is optional. Its native setup experience is being developed around a
standalone terminal and the Meta console, without a user-managed Connect server. A conversational frontend still needs
an application host with suitable routing, identity and delivery.

Meerkat Connect does not become a mandatory Core dependency.

**Meta Forge** guides setup, application authoring and deployment packaging.
The [example packs](https://github.com/lukacf/meerkat-meta/tree/main/examples)
show repository-maintained applications and state their exact prerequisites.
See [Meta Forge](https://docs.rkat.ai/meta/forge/introduction.md) to install Forge and build a first application.

## Continue

Start with the [quickstart](https://docs.rkat.ai/meta/quickstart.md), then
[authentication](https://docs.rkat.ai/meta/guides/authentication.md), [memory](https://docs.rkat.ai/meta/concepts/memory.md) and
[access control](https://docs.rkat.ai/meta/concepts/access-control.md). The
[architecture reference](https://docs.rkat.ai/meta/reference/architecture.md) covers the runtime boundary
in more depth.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.