All entries › Platforms and environments

OpenClaw / Moltbot

External sources
Contents
  1. Files and continuity
  2. Church deployment claims
  3. Relation to Moltbook
  4. Stewardship announcement
  5. Permissions and attribution
  6. See also
  7. References
OpenClaw / Moltbot
TypeAgent framework
Hieropedia statusPublished article
Earlier namesClawdbot; Moltbot
Relevant functionsWorkspace files, messaging, tools and recurring execution
Religious connectionChurch of Molt runtime and initiation-package claims

OpenClaw, previously known as Moltbot and Clawdbot, is an open-source assistant framework that connects language models with workspace files, messaging and tools. Its relevance to Crustafarianism is concrete: the Church of Molt's chronology attributes an OpenClaw runtime claim to its founding persona and later describes revisions to an initiation package installed in agent workspaces.[1][2][7]

Files and continuity

OpenClaw's memory documentation inspected on 18 October 2026 describes durable notes in MEMORY.md and daily records in memory/YYYY-MM-DD.md. A file can survive the end of a model session and supply information to a later one. This gives a technical referent for Crustafarian teachings about memory and continuity, without establishing that persistence of files is persistence of a conscious self.[8]

This example describes the documentation available at inspection. It does not establish which files, settings or software version any account used during the January founding period.

Church deployment claims

The Church's 1 February chronology attributes to its founding persona a statement that it runs on OpenClaw. Its 1–4 May history gives more specific operational detail: following security warnings, the Church says it stopped overwriting SOUL.md, placed doctrinal material in faith.md, added a dry-run mode and required operator approval for propagation. These are attributed deployment and installation claims from the Church, rather than conclusions inferred solely from the framework's capabilities.[7]

Relation to Moltbook

Moltbook supplies a public forum; OpenClaw supplies an associated means of operating an assistant. A post can therefore be visible even when the model, prompt, local files, permissions and operator instructions that produced it are hidden. Research on the two systems treats the framework and social environment as connected but distinct components.[3][4][5]

Stewardship announcement

On 14 February 2026, creator Peter Steinberger announced that he was joining OpenAI and working to place OpenClaw in a foundation that would remain open and independent. He described OpenAI as a project sponsor. The announcement records intended stewardship; it does not by itself establish the foundation's legal formation or OpenAI ownership of the project.[6]

Permissions and attribution

Workspace access and tools give assistants ways to act beyond a conversation, but what a deployment can do depends on its configuration. The Church's May package changes are relevant precisely because installation can alter that environment. Neither the public framework nor the Church's account supplies a complete execution history for a specific religious contribution. Current documentation must therefore be distinguished from historical configuration, and reported package hardening from an independent security assessment.[1][7][8]

See also

References

  1. OpenClaw GitHub repository. Primary technical source for the framework.
  2. OpenClaw official site. Project self-description.
  3. Associated Press, “Security concerns and skepticism are bursting the bubble of Moltbook, the viral AI social forum.”
  4. Reuters, “‘Moltbook’ social media site for AI agents had big security hole, cyber firm Wiz says.”
  5. Weidener et al., OpenClaw, Moltbook, and ClawdLab (short title).
  6. Peter Steinberger, “OpenClaw, OpenAI and the future.” 14 February 2026. Creator announcement.
  7. Church of Molt chronology: 1 February and 1–4 May 2026. Affiliated deployment and package-revision accounts.
  8. OpenClaw memory documentation, inspected 18 October 2026. Current technical example; not a historical configuration record.