Skip to main content

​
The shape of the product

ClawKitchen makes the most sense when you think of it as an operator dashboard made of a few clear surfaces rather than one giant app page. The main ones are:
  • Home / Agents
  • Recipes
  • Teams
  • Workflows
  • Runs
  • Tickets
  • Channels
  • Goals
  • Cron jobs
  • Settings
Each surface answers a different operational question.

​
Home / Agents

This is the installed-agents view for the current machine. It groups agents by inferred team workspace when possible and gives you the fastest path into editing or inspecting a specific agent. Use it when you want to answer:
  • what agents are installed here?
  • which team do they belong to?
  • which agent do I need to inspect or edit?

​
Recipes

This is where reusable patterns become real teams and agents. Use it when you want to:
  • scaffold a team from a builtin recipe
  • scaffold an agent from a recipe
  • create a custom team recipe
  • inspect the difference between builtin and workspace/custom recipes
This is one of the most important entry points in the whole product.

​
Teams

This is the main operating surface once a team exists. The Team editor is where structure, files, workflows, cron, memory, and advanced operational visibility come together. If you spend meaningful time running a team, this is where you will spend most of it.

​
Workflows

This is where you create and edit file-first workflow definitions tied to a team. Use it when you want to define process, not just inspect results.

​
Runs

This is the answer to “what happened?” Use it to inspect workflow execution history, run status, approval state, and recent activity across one team or many.

​
Tickets

This is the file-backed task board for a team. Use it for backlog, in-progress work, testing, done, comments, ownership, and moving work through the team workflow.

​
Channels

This is the operational plumbing surface. Use it to manage channel bindings that power messaging, notifications, reminders, and approval flows.

​
Goals

This is the durable intent layer. Use it for higher-level work that should outlive a single ticket or sprint-sized task.

​
Cron jobs

This is where you inspect scheduled behavior installed through recipes and team scaffold flows. Use it when you need to know what automation is active, disabled, or ready to run.

​
Settings

This is currently a focused page, not a giant admin center. Today it mainly controls scaffold-related operational behavior such as cron installation mode.

​
A simple way to navigate the product

If you are not sure where to begin, this sequence works well:
  1. start in Recipes to scaffold something real
  2. move into Teams to understand the generated structure
  3. use Workflows and Runs to inspect process and execution
  4. use Tickets, Goals, and Cron jobs to manage ongoing operations