Plugin

ClawKitchen

The operator layer for OpenClaw. Manage teams, workflows, plugins, files, approvals, and execution visibility from a UI built for daily use, not just initial setup.

Explore ClawRecipes GitHub

Team Builder

Create and edit teams and agent roles without living in CLI commands or scattered config files.

Managed Memory + Files

Operate workspace context, artifacts, and durable team knowledge from one place.

Trigger Workflows

Kick off manual, cron, and event-driven runs across multiple node types from one dashboard.

Plugin Operations

Install plugins and shape team setup from a UI that operators can actually use daily.

Quick Install

STEP 1

$openclaw plugins install @jiggai/kitchen

$openclaw gateway restart

STEP 2

Modify `openclaw.json`

"kitchen": {"enable":true}

STEP 3

Update kitchen config

"kitchen": {
  "enabled": true,
  "config": {
    "dev": false,
    "host": "<ipAddress>",
    "port": 7777,
    "authToken": "<your_password>",
    "qaToken": "<randomHash_if_using_qa>"
  }
},

Feature 1

A real operator console for agent teams

ClawKitchen turns an OpenClaw deployment into something operators can actually run. Instead of living across config files, terminal commands, and fragile tribal knowledge, teams get a single place to inspect roles, workflows, runs, artifacts, and the state of the system. It is the missing daily-use layer between raw capability and real operations.

●See the shape of the system without hunting through files
●Operate teams, workflows, and outputs from one place
●Give non-terminal-native operators a usable control surface

Feature 2

Workflow visibility that makes automation trustworthy

Agent systems get much easier to trust when you can see the work moving. ClawKitchen surfaces runs, approvals, outputs, and state transitions so workflows feel inspectable instead of magical. That matters when you want teams to use automation in the middle of real delivery, not just as a toy demo.

●Inspect workflow state and output artifacts
●Review approvals and intermediate steps clearly
●Make execution visible to the humans who own the outcome

Feature 3

The marketing plugin makes content ops a first-class workflow

One of the strongest examples of the plugin model is marketing operations. Instead of treating content work as scattered documents and manual social posting, the marketing plugin brings calendars, media, previews, approvals, and publishing into the same operational stack. It turns campaign work into a visible workflow with real leverage.

●Calendar-led planning and campaign execution
●Media uploads, library management, and reusable assets
●Preview, approval, and publishing flow in one system

Marketing plugin concept, content planning

Marketing plugin concept, plugin UI detail

Feature 4

Best when paired with ClawRecipes

ClawRecipes installs the operating model. ClawKitchen makes it usable day to day. Together they give teams both the repeatable structure and the operator experience they need. Recipes define how the system should work. Kitchen makes that system visible, navigable, and manageable once it is live.

●Recipes provide scaffolding and operational shape
●Kitchen provides visibility, editing, and day-to-day control
●Together they move OpenClaw from setup to adoption

Coming soon

Managed AI teams

Want a hands-on team to set up ClawKitchen, plugins, workflows, approvals, and team operations for you? Join the early list.

Request info and tell us what kind of managed team, workflow, or plugin help you want.