Skip to content

Z.E.N.AI that follows a recipe, not a conversation.

Calm dispatch for chaotic work.

Z.E.N.

Z.E.N. is a workflow engine. Define steps in a short file, run them on demand or on a schedule, from your terminal or your browser.

Z.E.N. is opening a founding community โ€‹

About ten people, building alongside Zain. Everyone gets the CLI hands-on the moment the binary drops, plus a direct line for feature requests, extensions, and integrations you wish existed. No support tickets, no waiting in line. If that sounds like the right way to meet a product, request a spot.

The pattern you already use, written down once โ€‹

You've already done this: opened your AI of choice, typed the same question for the fourth time this month, copied the answer into the same Notion page, fixed the same three things by hand. The work is repetitive. The tool isn't.

Z.E.N. is where you save the recipe. A workflow is a short file that lists the steps. AI does the heavy lifting at each step. You run it now, schedule it to repeat, or kick it off from inside your existing agent. The shape doesn't change between runs; only the inputs do.

Chat is for exploring. Z.E.N. is for repeating.

What people actually use it for โ€‹

A daily brief that scans Slack, Notion, and the calendar at 7 a.m. and lands a summary in the inbox. A research sprint that takes a topic, runs three rounds of search, drafts a memo. Meeting capture that pulls the transcript, extracts decisions, files them in Notion. A content workflow that turns a rough idea into a draft, a thumbnail brief, and a social post. You write the recipe once. It cooks while you do something else.

From inside your existing agent โ€‹

If you already live in Claude Code, OpenClaw, or Hermes, Z.E.N. is the infrastructure they reach for. They call your workflows by name. You don't switch tools to dispatch a job; you ask your agent to run the daily brief and it fires.

Where to go next โ€‹

AI that follows a recipe, not a conversation.