Appearance
The Big Picture: Welcome to Z.E.N.
Think of this system as an invisible kitchen manager. It doesn't cook the food itself, but it hands out the recipes, tells the cooks when to start, watches the clock, and makes sure the appetizers go out before the main course.
To understand how it works, you only need to know six basic ideas.
1. Workflow: The Recipe Book
A workflow is a recipe. It is a short text file where you write down the name of the dish, a description of what it is, and the exact steps needed to make it.
You can keep these recipes in two places: in the kitchen drawer for a specific project, or in your personal cookbook at home so you can use it anywhere on your machine. Every time the system starts, it looks in both places to see what recipes are available. It comes with a few basic starter recipes, but you can copy them, change them, or throw them in the trash if you do not need them.
2. Node: The Individual Steps
A node is a single step inside your recipe. Just like a kitchen recipe tells you to chop onions or bake for twenty minutes, a step here tells the system to do one specific action.
The main types of steps are:
- Prompt: Ask a smart assistant a question and wait for the answer.
- Bash: Give a direct command to the computer, like telling it to move a file.
- Subagent: Hand a tricky task over to another assistant or open up a separate recipe.
- Approval: Pause everything and wait for a human to say it is okay to keep going.
- Loop: Repeat the same step over and over with different ingredients.
Because some steps cannot happen until others are finished (you cannot bake the cake until you mix the batter), each step lists what it depends on. The system looks at these connections to figure out what steps can be done at the exact same time, and what steps have to wait in line.
3. Run: Cooking the Meal
A run is what happens when you actually execute the recipe. If a workflow is the blueprint for chocolate cake on paper, a run is the actual cake baking in the oven right now.
Every single run is isolated. It gets its own counter space, its own mixing bowls, and its own record log. If a run fails because the power blinked, you do not have to start over from scratch. You can restart it right from the step where it broke. You can watch all of this happening in real-time on a digital dashboard, clicking into any active meal to see exactly what is happening.
4. Schedule: The Alarm Clock
A schedule is an automated timer pinned to a specific recipe. It tells the manager to make a certain dish every Tuesday at 4:00 PM. The manager checks the clock every minute to see if anything is due.
If the timer goes off but the kitchen is still busy making that exact same dish from earlier, the manager notes the conflict and waits. If your computer was turned off when the timer was supposed to go off, you can set it to either skip that meal entirely or hurry up and play catch-up the moment the computer turns back on.
5. Provider: The Line Cooks
The provider is the specific AI brain doing the actual work for a single step. The system comes with a few built-in brains you might recognize, like Claude or Codex.
The clever part is that you choose the brain for each individual step, not for the whole recipe. You can have a very smart, detailed brain write a letter in step one, and a fast, cheap brain double-check the spelling in step two. If a new, better brain comes out tomorrow, you can swap it into your recipe by changing just one word without rewriting the whole step.
6. Agent: The Head Chef
An agent is an external AI tool that acts like the head chef. It lives outside of this system entirely. It looks at the big picture and tells the system to run a specific recipe right now.
To keep them straight: the agent stands outside the kitchen and orders the recipe to start. The provider is inside the kitchen, actually standing at the stove doing the work for that step.
Terms You Can Ignore for Now
As you get deeper into the system, you might bump into a few other words. Do not worry about memorizing these yet, as most people rarely need them:
- Codebase: The specific digital folder where your project lives.
- Worktree: A safety feature that makes a temporary copy of your files so an AI does not accidentally overwrite your real work while experimenting.
- Hook: An automated trigger that fires a recipe the instant something happens outside, like a customer submitting a form.
- MCP Server: An extra tool belt you plug into a step so a brain can look up web data or check a database.
- Skill: A pre-packaged bundle of instructions and tools that your external head chef knows how to use instantly.
The best approach is to avoid learning all of this at once. Look at how a run works, set up a schedule, and start building. Skip the complicated loops and tripwires until you find yourself trying to solve a problem that absolutely requires them.