Start a runtime
Connect an SDK, configure the application and open its console.
Choose your starting point
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
Memory is an agent capability, not just another chat history. Its
record and retrieval system 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 for the composition boundary.