Experimental OpenClaw plugins that are too playful, too specific, or too new for the monorepo. Small creatures live here: themes, composer critters, status vocabularies, dashboard toys. Everything is a normal OpenClaw plugin with an openclaw.plugin.json, so anything that grows up can move into the monorepo or ClawHub unchanged.
| Plugin | What it does |
|---|---|
redhat-theme |
A professional Red Hat look: Red Hat Red on neutral grays, the Red Hat type family, no lobster, a penguin in a fedora on the ledge, and build-and-deploy status words. |
lobster-theme |
A calm deep-sea Lobster look: ember and teal on black-teal or sand, Space Grotesk and Fraunces, one big line-art lobster across the canvas, and a composer with pincer-tip corners. |
git clone https://github.com/openclaw/tidepool.git
cd tidepool && pnpm install && pnpm build
openclaw plugins install ./plugins/redhat-themeThen pick the theme in Settings → Appearance, or ask the agent to switch to it. Native polish (fonts, artwork, hand-tuned tokens) loads only when Settings → Labs → Custom plugin UI is enabled; the portable palette works without it.
Use Node.js 24.22.1 or newer in the 24.x line and pnpm 12.15.0. Run pnpm install --frozen-lockfile, pnpm test, pnpm build, and pnpm check before submitting changes. Tests cover plugin reload ownership; the build type-checks and bundles each plugin, and the final check validates both built plugin manifests.
Create plugins/<name>/ with openclaw.plugin.json, a package.json named @openclaw/tidepool-<name>, and a README with one screenshot. Keep it self-contained: no shared runtime between plugins, no changes to OpenClaw itself. If a plugin needs a new theme or UI surface in OpenClaw, land that surface in the monorepo first and reference it here.
MIT. Names and marks of third parties (for example Red Hat) belong to their owners; themes here are community work, not affiliated with or endorsed by them.