The Spirit Index

Who holds the agent's memory, and can it be exported or moved?

Morpheus is a network, not one agent. Its desktop node keeps services, proxy-router data and the wallet store on the user's own machine, and the code is open source. Its docs say Smart Agents run on the user's laptop. Recovery depends on the user's mnemonic; no other export or backup procedure for local data is documented.

• MorpheusUI keeps downloaded services, proxy-router data and the wallet store in Electron's userData directory on the user's machine, protected by a local password.nodedocs.mor.org ↗
• Smart Agents run on the user's laptop with 8 to 16 GB of RAM.github.com ↗
• The consumer troubleshooting guide says to save the mnemonic phrase before a full reset.nodedocs.mor.org ↗

Does the identity survive any single platform?

Morpheus has open-source repositories under the MorpheusAIs GitHub organization, MIT-licensed, and documents its token contracts and community multisigs on Ethereum, Arbitrum and Base. The Ethereum multisig is named MOR.ETH on ENS.

• Docs list MOR token contracts on Ethereum, Arbitrum and Base, community multisigs on each chain, and the ENS name MOR.ETH for the Ethereum multisig.gitbook.mor.org ↗
• The Morpheus-Lumerin-Node repository is public under MorpheusAIs, MIT-licensed, not archived.api.github.com ↗

Does it run without heroics?

Morpheus code is under active development: the main node repository was last pushed on 3 November 2026. A proxy-router bug opened on 2 November 2026 has fixes merged to the dev branch and promoted to a test release.

• The Morpheus-Lumerin-Node repository shows pushed_at 2026-11-03.api.github.com ↗
• Issue 1011, opened 2 November 2026, has fixes merged to dev (PR 1032) and promoted as v7.19.10-test.github.com ↗

Can it transact?

The network transacts in MOR, whose token contracts are listed on Ethereum, Arbitrum and Base along with a community multisig on each chain. Users stake MOR to open inference sessions with providers, and unused stake returns when a session is closed.

• MOR token contracts: Ethereum 0xcbb8f1bda10b9696c57e13bc128fe674769dcec0, Arbitrum 0x092baadb7def4c3981454dd9c0a0d7ff07bcfc86, Base 0x7431ada8a591c955a994a21710752ef9b882b8e3, with community multisigs on each chain.gitbook.mor.org ↗
• Closing a session returns unused stake immediately; the used stipend becomes claimable after about one UTC day.nodedocs.mor.org ↗

Can its operator be checked?

Changes are proposed through Morpheus Requests for Comment (MRCs) in a public repository, discussed in a Discord forum, and given statuses such as Implemented or Under Discussion. Treasury and contracts are tied to community multisig accounts, but who signs them, and any pause or upgrade authority, is not documented.

• The MRC repository describes proposals to improve the Morpheus reference implementations, discussed on a dedicated Discord forum, with 91 MRCs listed by status.github.com ↗
• Docs list 'Community Multisignature Accounts' on each chain without naming signers, upgradeability or pause authority.gitbook.mor.org ↗
• Docs state agents should not be given private keys or allowed to make transactions on their own; users approve transaction payloads.github.com ↗

What happens when it dies mid-act?

Node operators have a documented recovery path: restart the proxy router, close stuck sessions to recover stake, and reset from the saved mnemonic. Bugs are tracked and fixed in public, as with a November 2026 issue where stake was locked in sessions the API reported as failed. No network-wide outage postmortem was found.

• The troubleshooting guide documents closing sessions to recover stake, restarting the proxy router, and resetting after saving the mnemonic.nodedocs.mor.org ↗
• Issue 1011 documents stake locked in sessions the API said did not exist, with fixes merged and promoted to a test release pending main.github.com ↗