Short version
- ClawRecipes = the plugin, commands, file-first workspaces, workflows, ticket flow
- ClawKitchen = the UI on top
What ClawKitchen is good at
ClawKitchen is useful for:- browsing teams and roles
- managing scaffolded teams
- seeing ticket lanes visually
- viewing workflow activity
- reviewing approvals
- guiding setup with a UI instead of raw files/CLI
What still lives in ClawRecipes
Even if you use ClawKitchen, the source of truth is still mostly file-first. ClawRecipes owns:- recipe scaffolding
- workspace layout
- ticket files
- workflow files
- workflow run artifacts
- CLI commands
Workflow note
Workflows depend on ClawRecipes features being present and, for some setups, on optional plugin/tooling being enabled after install. Examples:- LLM nodes may require the built-in
llm-taskplugin to be enabled - publish/posting behavior may require outbound posting config or a local patch
- the plugin is installed
- but an optional workflow dependency still needs to be enabled/configured
Good mental model
Think of it like this:- ClawRecipes builds and runs the machine
- ClawKitchen gives you the dashboard