Skip to main content
An instance is one memory design for one agent or use case, together with its API keys, people, and memories. Create separate instances for staging and production. Agents that serve the same users and do the same job can share an instance; otherwise, use separate instances. The use-case file defines the instance’s memory architecture. You cannot swap that design between unrelated use cases by reusing an instance.

​
Status and readiness

The Dashboard and CLI show these lifecycle statuses: Status is not readiness. A newly active instance can still be building its memory architecture. Wait until its build is ready before runtime reads or writes:
The default wait is 20 minutes. It exits 0 when ready, 7 on timeout, and 1 if the build fails. Builds usually take 15 to 20 minutes; Synap retries a failed attempt up to three times. After a final failure, you can run instances rebuild <instance-id> from the stored use case. Rebuilds are limited to three per instance in 24 hours and only work after a failure.

​
CLI list columns

maximem-synap instances list includes:
  • AGENT: the agent_type selected at creation: external_facing, intra_org, or special_purpose. Choose it according to who uses the agent.
  • CONFIG: the state of the memory architecture configuration.
  • BUILD: whether that configuration is still being built, ready, or failed.
Use --json when another program needs the full status and identifiers.