LucidClaw-PC — the Lucid-stack-aware build of OpenClaw

!LucidClaw Edge Workstation banner

LucidClaw-PC is the developer and company entry point into the Lucid stack — a branded derivative of OpenClaw that runs OpenClaw natively, stays compatible with its plugin contract, and adds a maintained, lane-managed integration target for the hosted Lucid stack.

If you are happy on stock OpenClaw, keep using it — no migration is required; LucidClaw is downstream of the same runtime. If you want a build that is co-developed with Lucid so version skew between cognition core and edge stays bounded, and that hosts upcoming Lucid-tier integrations as they ship, this is the build to pick up.

It runs as a daemon on your hardware, answers you on every messaging channel you already use, and reaches the hosted Lucid stack only through explicit, versioned service contracts. No Lucid internals live inside the local app.

> Status today: the lane is built; the Lucid-tier service contracts that > would justify switching from OpenClaw are still in development. See > docs/lucidclaw-public-lane.md § Lucid daemon > boundary for what is shipped vs. what is design intent.

Lane stance

LucidClaw-PC is a fresh fork into its own repo, by design:

• Repo split — public development lives in TheLucidTech/LucidClaw-PC; private operator/runtime proof work lives in TheLucidTech/LucidClaw.
• IP boundary — Lucidia_v1 stays private and untouched. This lane never pulls its history and is not a GitHub-level fork target for it.
• Clean rebrand — no mixed histories, no mixed authority between Lucidia internals and the public PC worker.
• Historical upstream base is OpenClaw — runtime base, channel SDK, plugin contract, and contributor record are preserved for attribution and compatibility while the public product name is LucidClaw-PC.
• Status: experimental / operational lane — kept this way until identity, registry, and CK-05 proof boundaries are clean.

| Layer | Name | Role | | ------------------- | ---------------- | -------------------------------------------------- | | PC build | LucidClaw-PC | Local worker, daemon, control plane (this repo) | | Private runtime | LucidClaw | Operator/runtime proof lane, not public source | | Hosted layer | Lucid stack | Persistence, feedback, premium utilities, research | | Historical upstream | OpenClaw | Runtime base, channels, plugin SDK, contributors | | Private core | Lucidia_v1 | Not in this repo. Not a fork target. IP boundary. |

CLI and runtime identifiers stay lucidclaw / openclaw for path, package, and config compatibility. Product-level naming is LucidClaw-PC.

Historical upstream: <https://github.com/openclaw/openclaw>.

Supported channels include: WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, IRC, Microsoft Teams, Matrix, Feishu, LINE, Mattermost, Nextcloud Talk, Nostr, Synology Chat, Tlon, Twitch, Zalo, Zalo Personal, WeChat, QQ, WebChat.

Vision · Public lane · Ship readiness

New install? Start with lucidclaw onboard.

Preferred setup: run lucidclaw onboard in your terminal. LucidClaw onboarding guides you step by step through setting up the gateway, workspace, channels, and skills. It is the recommended CLI setup path and works on macOS, Linux, and Windows (via WSL2; strongly recommended). Works with npm, pnpm, or bun.

Sponsors

LucidClaw sponsor and partner surfaces are not live in this fork yet. Historical upstream sponsor assets are intentionally not presented as LucidClaw sponsorship.

Subscriptions (OAuth):

• OpenAI (ChatGPT/Codex)

Model note: while many providers and models are supported, prefer a current flagship model from the provider you trust and already use. See Onboarding.

Install (recommended)

Runtime: Node 24 (recommended) or Node 22.16+.

npm install -g lucidclaw@latest
# or: pnpm add -g lucidclaw@latest

lucidclaw onboard --install-daemon
# legacy compatibility alias: openclaw onboard --install-daemon

LucidClaw onboarding installs the local Gateway daemon (launchd/systemd user service) so it stays running.

Quick start (TL;DR)

Runtime: Node 24 (recommended) or Node 22.16+.

Beginner setup is handled by lucidclaw onboard.

lucidclaw onboard --install-daemon

lucidclaw gateway --port 18789 --verbose

# Send a message
lucidclaw message send --target +1234567890 --message "Hello from LucidClaw"

# Talk to the assistant (optionally deliver back to any connected channel: WhatsApp/Telegram/Slack/Discord/Google Chat/Signal/iMessage/IRC/Microsoft Teams/Matrix/Feishu/LINE/Mattermost/Nextcloud Talk/Nostr/Synology Chat/Tlon/Twitch/Zalo/Zalo Personal/WeChat/QQ/WebChat)
lucidclaw agent --message "Ship checklist" --thinking high

Upgrading? Run lucidclaw doctor; legacy compatibility command: openclaw doctor.

Models config, auth profile rotation, and fallbacks remain local config surfaces.

Security defaults (DM access)

LucidClaw connects to real messaging surfaces. Treat inbound DMs as untrusted input.

Security defaults are local-first until a Lucid connection is explicitly enabled.

Default behavior on Telegram/WhatsApp/Signal/iMessage/Microsoft Teams/Discord/Google Chat/Slack:

• DM pairing (dmPolicy="pairing" / channels.discord.dmPolicy="pairing" / channels.slack.dmPolicy="pairing"; legacy: channels.discord.dm.policy, channels.slack.dm.policy): unknown senders receive a short pairing code and the bot does not process their message.
• Approve with: lucidclaw pairing approve <channel> <code> (then the sender is added to a local allowlist store).
• Public inbound DMs require an explicit opt-in: set dmPolicy="open" and include "*" in the channel allowlist (allowFrom / channels.discord.allowFrom / channels.slack.allowFrom; legacy: channels.discord.dm.allowFrom, channels.slack.dm.allowFrom).

Run lucidclaw doctor to surface risky/misconfigured DM policies.

Highlights

• Local-first Gateway — single control plane for sessions, channels, tools, and events.
• Multi-channel inbox — WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, IRC, Microsoft Teams, Matrix, Feishu, LINE, Mattermost, Nextcloud Talk, Nostr, Synology Chat, Tlon, Twitch, Zalo, Zalo Personal, WeChat, QQ, WebChat, macOS, iOS/Android.
• Multi-agent routing — route inbound channels/accounts/peers to isolated agents (workspaces + per-agent sessions).
• Voice Wake + Talk Mode — wake words on macOS/iOS and continuous voice on Android (ElevenLabs + system TTS fallback).
• Live Canvas — agent-driven visual workspace with A2UI.
• First-class tools — browser, canvas, nodes, cron, sessions, and Discord/Slack actions.
• Companion apps — macOS menu bar app + iOS/Android nodes.
• Onboarding + skills — onboarding-driven setup with bundled/managed/workspace skills.
• Lucid stack bridge — optional service contracts for hosted persistence,

premium utilities, feedback loops, and research-derived improvements without putting Lucid internals inside the local app.

Security model (important)

• Default: tools run on the host for the main session, so the agent has full access when it is just you.
• Group/channel safety: set agents.defaults.sandbox.mode: "non-main" to run non-main sessions inside sandboxes. Docker is the default sandbox backend; SSH and OpenShell backends are also available.
• Typical sandbox default: allow bash, process, read, write, edit, sessions_list, sessions_history, sessions_send, sessions_spawn; deny browser, canvas, nodes, cron, discord, gateway.
• Before exposing anything remotely, read Security, Sandboxing, and Configuration.

Operator quick refs

• Chat commands: /status, /new, /reset, /compact, /think <level>, /verbose on|off, /trace on|off, /usage off|tokens|full, /restart, /activation mention|always
• Session tools: sessions_list, sessions_history, sessions_send
• Skills registry: ClawHub
• Architecture overview: Architecture

Docs by goal

• New here: Getting started, Onboarding, Updating
• Channel setup: Channels index, WhatsApp, Telegram, Discord, Slack
• Apps + nodes: macOS, iOS, Android, Nodes
• Config + security: Configuration, Security, Sandboxing
• Remote + web: Gateway, Remote access, Tailscale, Web surfaces
• Tools + automation: Tools, Skills, Cron jobs, Webhooks, Gmail Pub/Sub
• Internals: Architecture, Agent, Session model, Gateway protocol
• Troubleshooting: Channel troubleshooting, Logging, Docs home

Apps (optional)

The Gateway alone delivers a great experience. All apps are optional and add extra features.

If you plan to build/run companion apps, follow the platform runbooks below.

macOS (LucidClaw.app) (optional)

• Menu bar control for the Gateway and health.
• Voice Wake + push-to-talk overlay.
• WebChat + debug tools.
• Remote gateway control over SSH.

Note: signed builds required for macOS permissions to stick across rebuilds (see macOS Permissions).

iOS node (optional)

• Pairs as a node over the Gateway WebSocket (device pairing).
• Voice trigger forwarding + Canvas surface.
• Controlled via lucidclaw nodes ....

Runbook: iOS connect.

Android node (optional)

• Pairs as a WS node via device pairing (lucidclaw devices ...).
• Exposes Connect/Chat/Voice tabs plus Canvas, Camera, Screen capture, and Android device command families.
• Runbook: Android connect.

From source (development)

Use pnpm for source checkouts. The repository is a pnpm workspace, and bundled plugins load from extensions/* during development so their package-local dependencies and your edits are used directly. Plain npm install at the repo root is not a supported source setup.

For the dev loop:

git clone <lucidclaw-repo-url>
cd LucidClaw

pnpm install

# First run only (or after resetting local LucidClaw config/workspace)
pnpm lucidclaw setup

# Optional: prebuild Control UI before first startup
pnpm ui:build

# Dev loop (auto-reload on source/config changes)
pnpm gateway:watch

If you need a built dist/ from the checkout (for Node, packaging, or release validation), run:

pnpm build
pnpm ui:build

pnpm lucidclaw setup writes the local config/workspace needed for pnpm gateway:watch. It is safe to re-run, but you normally only need it on first setup or after resetting local state. pnpm gateway:watch does not rebuild dist/control-ui, so rerun pnpm ui:build after ui/ changes or use pnpm ui:dev when iterating on the Control UI. If you want this checkout to run onboarding directly, use pnpm lucidclaw onboard --install-daemon.

Note: pnpm lucidclaw ... runs TypeScript directly (via tsx). pnpm build produces dist/ for running via Node or the packaged LucidClaw binary, while pnpm gateway:watch rebuilds the runtime on demand during the dev loop.

Development channels

• stable: tagged releases (vYYYY.M.D or vYYYY.M.D-<patch>), npm dist-tag latest.
• beta: prerelease tags (vYYYY.M.D-beta.N), npm dist-tag beta (macOS app may be missing).
• dev: moving head of main, npm dist-tag dev (when published).

Switch channels (git + npm): lucidclaw update --channel stable|beta|dev.

Agent workspace + skills

• Workspace root: ~/.openclaw/workspace (configurable via agents.defaults.workspace).
• Injected prompt files: AGENTS.md, SOUL.md, TOOLS.md.
• Skills: ~/.openclaw/workspace/skills/<skill>/SKILL.md.

Configuration

Minimal ~/.openclaw/openclaw.json (model + defaults):

{
  agent: {
    model: "<provider>/<model-id>",
  },
}

Full configuration reference (all keys + examples).

Star History


Product summary

LucidClaw-PC is the PC-side worker and workstation built by Lucid-tech: a local daemon that runs on consumer hardware, plugs into messaging channels, and reaches the Lucid stack only through service contracts. The digital eagle claw mark is the public character for this lane.

• PC build: LucidClaw-PC — this repo
• Private runtime lane: LucidClaw — operator/runtime proof work, not this repo
• Hosted layer: Lucid stack
• Company: Lucid-tech
• Historical upstream: OpenClaw
• Private core: Lucidia_v1 — separate, private, not merged here

Lucid-dependent internals stay behind Lucid service boundaries. The public app consumes only documented API contracts, usage receipts, entitlement state, and optional hosted persistence sync.

Community

See CONTRIBUTING.md for guidelines, maintainers, and how to submit PRs. AI/vibe-coded PRs welcome.

Special thanks to Mario Zechner for his support and for pi-mono. LucidClaw-PC preserves upstream OpenClaw attribution and license history while running a separate, public PC lane. The clawtributors wall below carries forward the upstream contributor record we ride on.

Thanks to all clawtributors:

<!-- clawtributors:start -->

                                                         [![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&s=48)](https://github.com/apps/github-actions)                                                                                                                                                                                                                                                                                                                                                                         [![Joshua McKiddy](https://