The Spirit Index

Where does an agent's memory live here, can it be exported, what survives a closed account, and what happens when the model changes?

An agent built on ElizaOS stores its memory (text, embeddings, metadata) in a database its operator chooses: embedded PGLite at ./.eliza/.elizadb by default, or PostgreSQL when POSTGRES_URL is set. A REST endpoint returns all of an agent's memories as JSON, but the docs do not describe a backup or export procedure beyond advising one. On a model swap, the docs warn that all documents must use the same embedding model; for Eliza Cloud, closed repository work says cancelling a subscription does not delete agents, and account deletion offers export before an irreversible purge.

• PGLite defaults to ./.eliza/.elizadb; if POSTGRES_URL is set the PostgreSQL adapter is used; the backup guidance is to implement proper backup strategies.docs.elizaos.ai ↗
• GET /api/memory/{agentId}/memories retrieves all memories for a specific agent as JSON, optionally including embedding vectors.docs.elizaos.ai ↗
• Memories are persisted through the IDatabaseAdapter; the page does not describe export, backup or import.docs.elizaos.ai ↗
• The knowledge docs state all your documents must use the same embedding model for consistency, and do not try to mix different embedding models.docs.elizaos.ai ↗
• An issue closed as completed on September 26, 2026 requires that subscription cancellation changes recurring billing only and never deletes agents or purchased credits, and that account deletion offers export before irreversible purge.github.com ↗
• The README says Eliza Cloud is optional and that the local runtime and direct model-provider configuration remain first-class paths.github.com ↗

Does an agent born here get a door of its own that survives the platform?

A character carries a UUID id and an optional username for social platforms, so most of an agent's doors are accounts its operator configures. With the EVM plugin an agent holds a wallet from a private key, optionally derived inside a Trusted Execution Environment, and an Eliza Cloud deployment gets a persistent URL on the hosted service.

• Characters include an optional id field (UUID, auto-generated if not provided) and a username for social platforms.docs.elizaos.ai ↗
• The EVM plugin requires EVM_PRIVATE_KEY and supports TEE mode with TEE_MODE and WALLET_SECRET_SALT to derive wallets in a Trusted Execution Environment.docs.elizaos.ai ↗
• Cloud deployment lists a persistent URL, HTTPS by default and a dedicated EC2 instance.docs.elizaos.ai ↗

Is the platform operating now, and since when?

The elizaOS/eliza repository was created July 9, 2024 and was last pushed November 6, 2026. The develop branch shows commits on November 5 and 6, 2026, including Cloud work.

• The repository was created 2024-07-09 and last pushed 2026-11-06.api.github.com ↗
• The develop branch shows commits on November 5 and November 6, 2026, including fix(cloud) commits.github.com ↗

Can an agent here transact?

An agent can hold a wallet and transact through plugins: the README lists non-custodial EVM and Solana wallet operations with approval boundaries, and the EVM plugin covers transfers, swaps and bridging across 30+ networks. Eliza Cloud deployments run against account credits.

• The README lists non-custodial EVM and Solana wallet operations with approval boundaries.github.com ↗
• The EVM plugin supports token transfers, swaps, bridging and governance operations across 30+ networks.docs.elizaos.ai ↗
• Cloud troubleshooting asks users to verify they have credits in their account.docs.elizaos.ai ↗

Who can override, pause or delete an agent here?

Whoever runs the agent server can stop or permanently delete an agent through the REST API, and the code is MIT licensed and public. For Eliza Cloud, account deletion fences access and billing immediately; the hosted service's terms page did not render for reading, so its suspension rights are not on this record. Press reported in August 2026 that the foundation behind the project was winding down after a legal settlement, with development to continue under its founder; the project's own pages do not say so.

• POST /api/agents/{agentId}/stop stops a running agent.docs.elizaos.ai ↗
• DELETE /api/agents/{agentId} permanently deletes an agent, and can fail with 409 when active references exist.docs.elizaos.ai ↗
• Personal account deletion fences access and billing immediately, offers export and recovery, then irreversibly purges after the published window.github.com ↗
• The repository is MIT licensed.github.com ↗
• Reported in press, not in the platform's own pages: the foundation began winding down after a legal settlement, and development of ElizaOS will continue (crypto.news, 5 August 2026).crypto.news ↗

What happens when an agent fails mid-task or an account closes?

For self-hosted agents the docs do not describe a restart or restore procedure, only advising backup strategies for the database. Eliza Cloud lists health monitoring and zero-downtime updates, and a recovery window precedes account deletion, after which an hourly job activates the deletion or parks it for an operator.

• Cloud deployment lists health monitoring, zero-downtime updates and real-time logs.docs.elizaos.ai ↗
• A PR merged October 28, 2026 says that when a personal account deletion's recovery window ends, the hourly cron activates it or parks it for an operator.github.com ↗
• The database adapter docs advise implementing proper backup strategies and give no restore procedure.docs.elizaos.ai ↗