Zenflow Concepts

Zenflow organizes AI-driven work into a small set of primitives. Understanding how they fit together makes everything else click.

​

Repositories

A repository is a connected codebase. Zenflow clones it, tracks its branches, and uses it as the scope for every Code task.

• Add from GitHub, create blank, or select a local folder
• Each repository has its own automation scripts and configuration
• Multiple repositories can run tasks simultaneously

​

Tasks

A task is the fundamental unit of work. When you create a task, Zenflow spins up an isolated environment and assigns an agent to execute it. Tasks support parallel execution — you can run as many as your machine allows, each in its own worktree.

​

Workflows

Workflows define the execution strategy for a task — how much planning happens, whether specs are generated, and how verification works. Work mode has its own set: Auto, Brainstorm, Deep Brainstorm, Research, and Write.

​

Git Worktrees

Every Code task runs in its own Git worktree — a separate checkout of the repository with its own branch. This is how Zenflow achieves true parallel execution without conflicts.

• Created automatically at .zenflow/worktrees/{task_id}
• Agents read, write, and commit inside the worktree
• Your main working directory is never touched
• Cleaned up when you archive or delete a task

​

Agents and Presets

An agent is the AI runtime that executes task steps. Zenflow supports multiple agent backends, and you configure them via presets. Presets are managed in Settings → Saved presets and can be selected per-task or per-step.

​

Verification

Zenflow can run verification scripts after each agent turn to catch issues early:

• Configured per-repository in Repository Configuration
• Runs linting, type checks, tests, or custom scripts
• Failures are fed back to the agent for self-correction
• Keeps the feedback loop tight so errors don’t compound

​

Automations

Automations let you schedule recurring tasks — either at the workspace level (cron-style) or inside an existing task (interval-based agent sessions).

​

Next Steps