Related Pages

Related topics: Channels and Messaging Integrations, AI Providers, Plugins, and Skills, Companion Apps and Nodes

OpenClaw Overview and Gateway Architecture

1. Project Purpose and Scope

OpenClaw is a modular AI agent platform shipped as a monorepo of plugins, core packages, and harness integrations. The repository is structured around a @openclaw/plugin-sdk workspace package that every first-party extension depends on, providing a common plugin contract, typebox schemas, and zod-based validation, and a shared openclaw host peer dependency. Source: extensions/memory-wiki/package.json, extensions/codex/package.json, extensions/feishu/package.json.

The 2026.6.2 release line currently declared across extension manifests is the latest published generation; the core is explicitly described as entering Stabilisation Mode by maintainers, who have stated that new feature requests will be closed (and auto-closed) while bug reports remain welcome. Source: community context for issue #5799 "OpenClaw: Stabilisation Mode".

The platform's main audiences are:

• Agent authors who need pluggable model providers, memory layers, and workflow tools.
• Channel integrators who need Slack-class, enterprise messenger, and synthetic transports.
• Operators who need typed pipelines, supervision, and OpenTelemetry-based observability.

2. Plugin / Extension Architecture

Every extension follows the same manifest shape under the top-level openclaw key in its package.json. The extensions field lists entry points (e.g. ./index.ts), and most extensions add a setupEntry, channel, or install block describing how the host should load and surface them. Source: extensions/feishu/package.json, extensions/mattermost/package.json, extensions/qa-channel/package.json.

The first-party catalog is intentionally narrow and grouped by role. The table below summarises the extensions visible in the repository.

Sources: extensions/codex/package.json, extensions/codex-supervisor/package.json, extensions/memory-wiki/package.json, extensions/feishu/package.json, extensions/mattermost/package.json, extensions/qa-channel/package.json, extensions/tlon/README.md, extensions/lobster/package.json, extensions/diagnostics-otel/package.json, extensions/web-readability/package.json.

Two adjacent packages extend the runtime beyond plugin boundaries:

• packages/markdown-core provides the shared markdown IR, frontmatter, fences, and render-aware chunking primitives consumed by extensions that manipulate agent-visible text. Source: packages/markdown-core/package.json.
• extensions/open-prose ships a standard library of .prose programs for evaluation, memory, and improvement loops, treating each program as a production-quality workflow artefact. Source: extensions/open-prose/skills/prose/lib/README.md.

3. Gateway RPC Surface

The host exposes a JSON-RPC-style gateway through which agent loops, CLIs, and the setup wizard invoke extension behaviour. The clearest documented surface is the memory-wiki plugin, which registers both read and write methods against the gateway namespace. Source: extensions/memory-wiki/README.md.

Read methods:

• wiki.status, wiki.doctor, wiki.search, wiki.get
• wiki.obsidian.status, wiki.obsidian.search

Write methods:

• wiki.init, wiki.compile, wiki.ingest, wiki.lint
• wiki.bridge.import, wiki.unsafeLocal.import, wiki.apply
• wiki.obsidian.open, wiki.obsidian.command, wiki.obsidian.daily

The same plugin also publishes an agent-tool surface (wiki_status, wiki_lint, wiki_apply, wiki_search, wiki_get) so that running agents can address the wiki directly, and a non-exclusive memory corpus supplement so shared memory_search / memory_get flows can reach the wiki when the active memory plugin supports corpus selection. The wiki_apply method accepts structured claims payloads, allowing the wiki to store claim-level evidence rather than only page-level prose. Source: extensions/memory-wiki/README.md.

4. Platform Support and Community Direction

OpenClaw's user-facing node applications (macOS, iOS, Android) are referenced in community issue #75, which is a long-standing request to ship equivalent Linux and Windows "Clawdbot" clients. As of the current release line no Linux or Windows first-party app is published from this monorepo, so users on those platforms currently rely on the CLI host and channel plugins rather than a native node. Source: community context for issue #75.

Channel-coverage gaps are also visible at onboarding. Issue #26534 requests that DingTalk be offered as an option in the first-install channel wizard, even though DingTalk transport support has already landed. Issue #8650, in turn, requests swapping the built-in Feishu plugin for the community-preferred @m1heng/clawdbot-feishu; the manifest declares the current Feishu extension to be community-maintained by @m1heng, but several features requested in that thread are still tracked separately. Source: community context for issues #8650 and #26534; extensions/feishu/package.json.

Finally, the 2026.6.5-beta.2 highlights illustrate how the gateway/channel stack is hardening in stabilisation mode: QQBot strips raw <thinking> scaffolding before native delivery, and the MCP tool-result materialiser coerces resource_link, resource, audio, and malformed image blocks at the boundary to prevent upstream 400s and poisoned sessions. Source: community context for release openclaw 2026.6.5-beta.2.

See Also

• Memory Wiki vault and claim/evidence model — extensions/memory-wiki/README.md
• Codex app-server provider and supervisor — extensions/codex/README.md, extensions/codex-supervisor/package.json
• OpenProse standard library and improvement loop — extensions/open-prose/skills/prose/lib/README.md
• Shared markdown IR package — packages/markdown-core/package.json

Related Pages

Related topics: OpenClaw Overview and Gateway Architecture, AI Providers, Plugins, and Skills

Channels and Messaging Integrations

Purpose and Scope

OpenClaw's channels are external messaging transports that connect a single OpenClaw gateway to chat platforms used by humans and teams. Each channel is delivered as an independent plugin under extensions/ and is loaded through a shared openclaw plugin manifest, so adding or removing a chat surface never requires touching the core runtime.

The channel subsystem is intentionally narrow: it owns transport (Socket Mode bots, webhook receivers, official platform APIs), per-channel session/command surface, and channel-specific configuration. Routing, pairing, and the agent loop live elsewhere; the channel is the adapter between the platform and OpenClaw's gateway RPC. This is why each plugin's package.json declares a channel block rather than full plugin behavior.

Plugin Catalog

Every messaging integration in the repo follows the same plugin shape: an extensions/<id>/ folder, an index.ts extension entry, a setupEntry.ts for onboarding, and a channel block inside the openclaw manifest. The catalog below is taken directly from the per-plugin package.json files at the time of writing.

The manifest pattern is uniform. Every channel plugin declares the same five fields in its openclaw.channel block: id, label, selectionLabel, docsPath, and blurb, plus optional fields for aliases, order, systemImage, markdownCapable, commands, cliAddOptions, and configuredState. The same pattern is what makes openclaw setup and openclaw add able to enumerate every chat surface without hard-coding.

Channel Configuration Model

A channel plugin is wired into the host via three manifest sections:

1. install — npmSpec, defaultChoice (typically "npm"), and a minHostVersion floor such as ">=2026.5.28". Source: extensions/slack/package.json
2. compat — a pluginApi lower bound (commonly ">=2026.6.2") that the host checks before loading the plugin. Source: extensions/discord/package.json
3. channel — the per-platform descriptor seen above, plus a configuredState block that tells the host how to detect "already configured" without parsing config files. Discord, for example, is configured when DISCORD_BOT_TOKEN is set in the environment. Source: extensions/discord/package.json

Tlon additionally ships a richer CLI onboarding surface: cliAddOptions defines flags like --ship, --code, --group-channels, --dm-allowlist, and --auto-discover-channels, which openclaw add tlon forwards directly to the setup wizard. Source: extensions/tlon/package.json

Slack opts into deferConfiguredChannelFullLoadUntilAfterListen in startup, so a configured Slack Socket Mode socket only fully loads after the gateway has begun listening. This keeps reconnect and TLS handshake behavior isolated from the listen path. Source: extensions/slack/package.json

Node, Apps, and Channel Endpoints

Channels run inside the gateway, but the gateway is reached by nodes — the macOS, iOS, and Android companion apps. The iOS app's README describes a typical end-to-end flow: the phone pairs with the gateway, the gateway is configured against one or more channels, and a wake/reconnect cycle keeps the node-side socket alive across scene transitions. Source: apps/ios/README.md

Open community issue #75 ("Linux/Windows Clawdbot Apps") highlights that macOS, iOS, and Android are the only official nodes today. Linux and Windows nodes are still missing, which means desktop users typically interact with channels through the CLI or a third-party node rather than a first-party desktop app. See: openclaw#75.

Community-Driven Channel Surface

The channel catalog is shaped as much by community demand as by core roadmap. A few representative threads:

• Feishu plugin selection — Issue #8650 requests replacing the built-in Feishu plugin with the more featureful community-maintained @m1heng/clawdbot-feishu. The shipped @openclaw/feishu already credits @m1heng in its description field, but the issue is still active, so the parity gap is real. See: openclaw#8650. Source: extensions/feishu/package.json
• DingTalk onboarding — Issue #26534 points out that DingTalk channel support exists upstream, but it is not yet presented as an option in the first-time setup wizard. Users currently have to add it manually after install. See: openclaw#26534.
• QQBot reasoning leakage — The 2026.6.5-beta.2 release notes record that QQBot now strips model reasoning/thinking scaffolding before native delivery, so raw <thinking> content no longer leaks into channel replies. This is a channel-specific sanitization concern, not a runtime change. Source: extensions/qqbot/package.json
• Stabilisation mode — Issue #5799 declares the project is in stabilisation: new channel feature requests are auto-closed, while bug reports stay open. This sets the expectation that the channel list will be reviewed for quality rather than expanded rapidly. See: openclaw#5799.

Operational Notes

• qa-channel is intentionally hidden from the user-facing catalog: its exposure block sets configured, setup, and docs to false. It exists only to drive automated QA scenarios and must not be presented in openclaw add or the setup wizard. Source: extensions/qa-channel/package.json
• configuredState env hints let the host distinguish "user has not run setup" from "user has run setup but lost config". Discord uses a single required env var; Slack accepts any of three tokens, reflecting the multiple ways a Slack app can be wired. Source: extensions/discord/package.json and extensions/slack/package.json
• markdownCapable: true is a hint, not a guarantee: it tells the agent that the channel renders markdown, but the host may still down-render for quoted replies or thread contexts. Only Discord, Slack, and ClickClack opt into this flag today. Source: extensions/discord/package.json

See Also

• openclaw#75 — Linux/Windows Clawdbot Apps
• openclaw#5799 — OpenClaw: Stabilisation Mode
• openclaw#8650 — Switch Built-in Feishu Plugin to @m1heng/clawdbot-feishu
• openclaw#26534 — Add DingTalk as a first-install channel option
• openclaw 2026.6.5-beta.2 release notes

Related Pages

Related topics: OpenClaw Overview and Gateway Architecture, Channels and Messaging Integrations

AI Providers, Plugins, and Skills

Overview

OpenClaw is structured as a host runtime that loads discrete plugins to add behavior. Three categories of plugin ship or can be installed:

1. AI Provider plugins — bind the host to a model runtime (for example, OpenAI Codex app-server).
2. Channel / integration plugins — bridge user-facing surfaces such as Telegram, Slack, QQ Bot, ClickClack, Zalo, or the synthetic qa-channel.
3. Skill packages — add domain workflows, such as the OpenProse VM and its standard library, or @openclaw/memory-wiki for persistent knowledge compilation.

Every plugin is published as an npm package, declared through a manifest in package.json, and is gated by a minHostVersion and a pluginApi compatibility range. The host then loads ./index.ts (or a built equivalent) and optionally a setupEntry for first-run wizards. Source: extensions/codex/README.md:1-15, extensions/memory-wiki/package.json:1-25

graph LR
  Host[OpenClaw Host<br/>Gateway + Runtime] --> Prov[AI Provider Plugin<br/>e.g. @openclaw/codex]
  Host --> Ch[Channel Plugin<br/>telegram · slack · qqbot · zalouser · clickclack · qa-channel]
  Host --> Sk[Skill Package<br/>open-prose · memory-wiki · diffs-language-pack]
  Prov --> Model[Model Turns<br/>media · overlays]
  Ch --> U[Users on chat surfaces]
  Sk --> Agent[Agent Workflows<br/>compilation · orchestration]

AI Provider Plugins

Provider plugins expose the catalogs and runtime surfaces of a model backend to OpenClaw agents. The canonical example is @openclaw/codex, the official provider plugin for the OpenAI Codex app-server.

The Codex plugin is installed from the host CLI with openclaw plugin add @openclaw/codex and is used whenever the host needs to run Codex-backed model turns, media understanding, and prompt overlays through the Codex app-server harness. It is the only first-party path to the Codex-managed GPT model catalog within OpenClaw. Source: extensions/codex/README.md:1-15

Provider manifests declare no channel block but still respect the standard compat.pluginApi constraint, so the host can refuse to load a provider built against a newer plugin API than the running gateway supports.

Channel and Integration Plugins

Channel plugins attach OpenClaw to a messaging surface. Each one declares a channel object in its manifest, including id, label, selectionLabel, detailLabel, docsPath, docsLabel, blurb, and a systemImage SF Symbol. The blurb field is what users see in the channel picker and during onboarding — a recurring community pain point: the DingTalk implementation exists, but because its selection entry is missing from the install wizard, new users cannot pick it on first install. Source: extensions/slack/package.json:30-55, extensions/qqbot/package.json:25-45

Manifests also encode commands.nativeCommandsAutoEnabled, commands.nativeSkillsAutoEnabled, and a configuredState probe that the host uses to decide whether to show the channel as already configured (matching by env keys such as TELEGRAM_BOT_TOKEN or SLACK_*_TOKEN). Source: extensions/telegram/package.json:1-20, extensions/slack/package.json:30-55

Skill Packages

Skills are the workflow layer. The OpenProse skill ships a full VM, a standard library, and a catalog of runnable examples.

The OpenProse standard library provides production programs for evaluation and improvement, including inspector.prose, vm-improver.prose, program-improver.prose, cost-analyzer.prose, calibrator.prose, and error-forensics.prose. Memory is split into user-memory.prose (cross-project personal memory) and project-memory.prose (project-scoped institutional memory). Together they form a recursive improvement loop: a program runs, the inspector analyzes fidelity, the VM improver proposes runtime PRs, the program improver proposes source PRs, and the cycle repeats. Source: extensions/open-prose/skills/prose/lib/README.md:1-30

The OpenProse examples are organized into themed packs: Basics (01–08), Agents & Skills (09–12), Variables & Composition (13–15), Parallel Execution (16–19), Loops (20), Pipelines (21), Error Handling (22–23), and advanced patterns beyond 24. The pack documents the language's design intent, including a "Captain's Chair" orchestration pattern in which a coordinating agent dispatches specialized subagents and never writes code directly. Source: extensions/open-prose/skills/prose/examples/README.md:1-60

A separate skill, @openclaw/memory-wiki, compiles durable knowledge into an Obsidian-friendly markdown vault. It exposes three modes — isolated (default), bridge (reads public memory artifacts through public seams), and unsafe-local (same-machine escape hatch) — and registers read tools (wiki_status, wiki_lint, wiki_search, wiki_get, wiki_apply) plus CLI commands such as openclaw wiki compile, openclaw wiki obsidian search "alpha", and openclaw wiki apply synthesis "Alpha Summary". The plugin also supplements the shared memory_search corpus so agents can reach the wiki through the active memory plugin. Source: extensions/memory-wiki/README.md:1-60

Plugin Manifest and Lifecycle

Every plugin carries a common manifest shape inside package.json:

• openclaw.extensions — entry points, e.g. ["./index.ts"].
• openclaw.setupEntry — optional first-run wizard.
• openclaw.compat.pluginApi — minimum supported plugin API.
• openclaw.install — npmSpec, defaultChoice, minHostVersion, localPath for in-repo extensions.
• openclaw.build.openclawVersion and bundledDist — host version the bundle was built against.
• openclaw.release.publishToClawHub and publishToNpm — distribution channels.

Source: extensions/memory-wiki/package.json:1-25, extensions/qqbot/package.json:25-45, extensions/slack/package.json:55-75

Support packages follow the same conventions. @openclaw/markdown-core is the shared markdown IR / rendering kernel consumed by view layers and the diffs viewer; it is a private workspace package exposed through subpath exports such as ./frontmatter, ./fences, ./code-spans, ./ir, ./render, and ./render-aware-chunking. Source: packages/markdown-core/package.json:1-25

A language pack extension, @openclaw/diffs-language-pack, illustrates a non-agent extension: it contributes static viewer assets only, requires @openclaw/diffs to be installed first, and pins minHostVersion: 2026.5.27. The host must be restarted after install or update. Source: extensions/diffs-language-pack/README.md:1-25

In the current Stabilisation Mode (announced in the community), new plugin feature requests are closed; the maintainers are locking down the core so the host and existing plugins remain reliable. Bug reports are still welcome, which is the recommended channel for reporting manifest regressions or missing first-install channel options such as DingTalk. Source: community discussion #5799.

See Also

• OpenClaw Memory & Wiki Systems
• OpenProse Orchestration
• Channel Integrations

Related Pages

Related topics: OpenClaw Overview and Gateway Architecture

Companion Apps and Nodes

Overview

OpenClaw's companion apps are the desktop and mobile clients that connect a user's device to the OpenClaw runtime. They register as nodes in the OpenClaw network, providing a local surface for the agent to interact with the host device while the core Gateway runs elsewhere. According to community discussion, the currently supported platforms are macOS, iOS, and Android, with Linux and Windows notably absent (Source: Issue #75).

The companion apps are described as "simpler nodes" in community discussions, suggesting they expose a streamlined subset of capabilities compared to the full Gateway runtime. They let users interact with OpenClaw agents from their personal devices while heavier agent logic runs on a server or in the cloud. Each platform's installation, configuration, and capability surface is documented separately under docs/platforms/ (Source: docs/platforms/index.md).

Platform Support

Currently Available

The macOS companion is referenced as the benchmark for what users expect on other platforms — community members have asked that "Linux and Windows" offer a "similar feature set to macOS ideally" (Source: Issue #75).

Missing Platforms

Issue #75, titled "Linux/Windows Clawdbot Apps," has accumulated 109 comments with no reactions, making it the highest-engagement community thread about platform coverage. Users have explicitly requested that the missing platforms match macOS capability as closely as possible (Source: Issue #75).

Architecture and Integration

Companion apps are distinct from channels in the OpenClaw plugin model. Channels are messaging transports — Telegram, Synology Chat, and ClickClack all register as channels and use the channel.* metadata block in their package.json to declare their identity, docs path, and ordering in the setup wizard (Source: extensions/synology-chat/package.json).

Nodes, by contrast, are device-local surfaces that the agent can drive directly. The companion apps occupy this node role, while providers like the Codex app-server integration sit behind a different plugin type and do not function as user-facing device companions (Source: extensions/codex/README.md).

graph LR
    Gateway[OpenClaw Gateway] --> MacNode[macOS Node]
    Gateway --> iOSNode[iOS Node]
    Gateway --> AndroidNode[Android Node]
    Gateway --> LinuxNode[Linux Node - Missing]
    Gateway --> WinNode[Windows Node - Missing]
    Gateway --> TG[Telegram Channel]
    Gateway --> SY[Synology Chat Channel]
    Gateway --> CC[ClickClack Channel]
    MacNode -. Node Protocol .-> Gateway
    iOSNode -. Node Protocol .-> Gateway
    AndroidNode -. Node Protocol .-> Gateway
    style LinuxNode fill:#fdd,stroke:#c00
    style WinNode fill:#fdd,stroke:#c00

The node concept is broader than just the companion apps — docs/nodes/index.md is the canonical entry point for the node protocol, lifecycle, and integration patterns (Source: docs/nodes/index.md). Plugins that interact with persistent state, such as @openclaw/memory-wiki, also depend on the same plugin SDK and shared seams that node implementations consume (Source: extensions/memory-wiki/README.md).

Current Status and Community Concerns

The project entered Stabilisation Mode as announced in Issue #5799. The maintainers explained: "We're getting a PR roughly every two minutes… we're locking down the core to make it rock solid. New feature requests will be closed (and soon auto-closed). Bug reports are still welcome" (Source: Issue #5799). Under this policy, the long-standing Linux/Windows companion request is unlikely to be accepted as a new feature, though related bug reports on the existing macOS/iOS/Android apps remain in scope.

The latest published build, openclaw 2026.6.5-beta.2, focuses on channel and runtime hardening — for example, QQBot now strips model reasoning scaffolding before native delivery, and MCP tool results coerce non-text/image blocks at the materialize boundary. These changes affect channel-side delivery rather than node-side capability, so the companion apps are unaffected by this particular release's behavioural changes.

Because the Stabilisation Mode freezes new surface area, operators who need a Linux or Windows node should track Issue #75 for status rather than opening parallel feature requests, and prioritise bug reports on the existing three platforms.

See Also

• Channels and messaging transports
• Plugin SDK and extension metadata
• Gateway RPC reference
• Node protocol (docs/nodes/)

Doramagic Pitfall Log

Found 22 structured pitfall item(s), including 2 high/blocking item(s). Top priority: Installation risk - Installation risk requires verification.

1. Installation risk: Installation risk requires verification

• Severity: high
• Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
• User impact: May increase setup, validation, or first-run risk for the user.
• Recommended check: Reproduce the official install and quickstart path in an isolated environment.
• Evidence: community_evidence:github | cevd_1e9d3aadd9b7439891ac5a663c132e20 | https://github.com/openclaw/openclaw/issues/90953

2. Security or permission risk: Security or permission risk requires verification

• Severity: high
• Finding: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
• User impact: May increase setup, validation, or first-run risk for the user.
• Recommended check: Reproduce the official install and quickstart path in an isolated environment.
• Evidence: community_evidence:github | cevd_ebe1d77d782b4c4381cb60880e73e967 | https://github.com/openclaw/openclaw/issues/91079

3. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: [Bug]: requiresReasoningContentOnAssistantMessages missing from ModelCompatSchema — can't replicate native DeepSeek behavior on custom providers
• User impact: Developers may fail before the first successful local run: [Bug]: requiresReasoningContentOnAssistantMessages missing from ModelCompatSchema — can't replicate native DeepSeek behavior on custom providers
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: [Bug]: requiresReasoningContentOnAssistantMessages missing from ModelCompatSchema — can't replicate native DeepSeek behavior on custom providers. Context: Observed when using node, linux
• Evidence: failure_mode_cluster:github_issue | fmev_d724d043b4cac87bb34d373786f48074 | https://github.com/openclaw/openclaw/issues/89660

4. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: [Feature]: [Feature Request] Native payment support for AI agents via HTTP 402
• User impact: Developers may fail before the first successful local run: [Feature]: [Feature Request] Native payment support for AI agents via HTTP 402
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: [Feature]: [Feature Request] Native payment support for AI agents via HTTP 402. Context: Observed when using node, python
• Evidence: failure_mode_cluster:github_issue | fmev_89a313a658203bd90540bbd4ca78130e | https://github.com/openclaw/openclaw/issues/91079

5. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.5.31-beta.2
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.5.31-beta.2
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.5.31-beta.2. Context: Observed when using node, docker
• Evidence: failure_mode_cluster:github_release | fmev_37cd300e078cb36a2813e08c0ca6dae0 | https://github.com/openclaw/openclaw/releases/tag/v2026.5.31-beta.2

6. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.5.31-beta.3
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.5.31-beta.3
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.5.31-beta.3. Context: Observed when using node, docker
• Evidence: failure_mode_cluster:github_release | fmev_a7b475dddb59089369065fedac8f4999 | https://github.com/openclaw/openclaw/releases/tag/v2026.5.31-beta.3

7. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.5.31-beta.4
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.5.31-beta.4
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.5.31-beta.4. Context: Observed when using node, docker
• Evidence: failure_mode_cluster:github_release | fmev_607d979b3caf7dae4f8f7d260d061ea8 | https://github.com/openclaw/openclaw/releases/tag/v2026.5.31-beta.4

8. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.6.1
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.6.1
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.6.1. Context: Observed when using node, docker, linux
• Evidence: failure_mode_cluster:github_release | fmev_6b9ef70fc1d9b84229d0ce9eea9e9b4d | https://github.com/openclaw/openclaw/releases/tag/v2026.6.1

9. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.6.1-beta.1
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.6.1-beta.1
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.6.1-beta.1. Context: Observed when using node, docker
• Evidence: failure_mode_cluster:github_release | fmev_9473262162f57db73e84e3cf9bb5b6a5 | https://github.com/openclaw/openclaw/releases/tag/v2026.6.1-beta.1

10. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.6.1-beta.2
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.6.1-beta.2
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.6.1-beta.2. Context: Observed when using node, docker, linux
• Evidence: failure_mode_cluster:github_release | fmev_71093596cc37d4d64e5bb8cd3e060330 | https://github.com/openclaw/openclaw/releases/tag/v2026.6.1-beta.2

11. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.6.1-beta.3
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.6.1-beta.3
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.6.1-beta.3. Context: Observed when using node, docker, linux
• Evidence: failure_mode_cluster:github_release | fmev_e98ec8b4469a7d77c603d3ae8ceef0e1 | https://github.com/openclaw/openclaw/releases/tag/v2026.6.1-beta.3

12. Installation risk: Installation risk requires verification

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: openclaw 2026.6.2-beta.1
• User impact: Upgrade or migration may change expected behavior: openclaw 2026.6.2-beta.1
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: openclaw 2026.6.2-beta.1. Context: Observed when using node, docker, windows, macos
• Evidence: failure_mode_cluster:github_release | fmev_c540b672ef221deb20719b44d5f31830 | https://github.com/openclaw/openclaw/releases/tag/v2026.6.2-beta.1

Community Discussion Evidence

Doramagic exposes project-level community discussion separately from official documentation. Review these links before using openclaw with real data or production workflows.

• Add OAuth support to the built-in xAI provider - github / github_issue
• [[Bug]: installing error message "WSL version output did not include a pa](https://github.com/openclaw/openclaw/issues/90953) - github / github_issue
• [[Feature]: [Feature Request] Native payment support for AI agents via HT](https://github.com/openclaw/openclaw/issues/91079) - github / github_issue
• [[Bug]: requiresReasoningContentOnAssistantMessages missing from ModelCom](https://github.com/openclaw/openclaw/issues/89660) - github / github_issue
• openclaw 2026.6.5-beta.2 - github / github_release
• openclaw 2026.6.5-beta.1 - github / github_release
• openclaw 2026.6.2-beta.1 - github / github_release
• openclaw 2026.6.1 - github / github_release
• openclaw 2026.6.1-beta.3 - github / github_release
• openclaw 2026.6.1-beta.2 - github / github_release
• openclaw 2026.6.1-beta.1 - github / github_release
• openclaw 2026.5.31-beta.4 - github / github_release