Projects and Goals Management

Zenborg structures your development work into Projects and Goals. This structure keeps repositories organized and isolates dependencies.

Workspace Projects

A Project in Zenborg maps to a Git repository on your local computer.

Project Root Directory (cwd): The working directory where Zenborg inspects code, reads configuration files, and spawns loop worktrees.
Projects Filter: In the Loops interface, use the project dropdown selector to switch views and view active runs.
File System Boundary: By default, agents are restricted to the project root directory. If an agent needs to touch files outside the repository (for example, shared monorepo packages or global configs), you must explicitly check "Allow outside project folder" in the loop setup panel.

Goals and Sub-Goals

The Goals interface (goals.html) provides high-level milestone management for larger projects.

Configuring a Goal

When creating or editing a goal, you define:

Manager Agent & Model: The agent responsible for architectural planning, synthesizing reviews, and verifying code quality.
Worker Agent & Model: The worker agent that performs plan reviews, writes code in the worktree, and runs tests.
Auto-advance: A toggle checkbox allowing Zenborg to automatically start subsequent sub-goals upon successful verification of preceding steps.
Max Correction Rounds: Configurable from 0 to 10 rounds (default 4).

Planning Options

Plan with Manager: Let the selected Manager Agent inspect the repository and generate proposed sub-goals automatically.
I have my own plan: Paste markdown or JSON directly into the plan input area.
Structure with Manager: When using your own plan, checking this option lets the Manager Agent format your text into structured, executable sub-goals.

Execution Views

Draft sub-goals: Review, re-order, or add sub-goals before execution starts.
Progress: Track which sub-goals are pending, in-flight, completed, or failed.
Timeline: An chronological event log recording when each agent started and completed work.
Review & merge: Inspect unified diffs across completed milestones before integrating them into your main branch.

Free Plan Boundaries

Zenborg includes a permanent Free tier that allows developers to run loops without purchasing a license. The Free tier enforces specific limits defined in lib/licence/entitlements.js:

Resource	Free Tier Limit	Pro / Beta Tier	UI Enforcement Message
Projects	`1` Project	Unlimited	`"Free plan: 1 project. Upgrade to unlock more."`
Active Loops	`1` Running Loop	Up to `8` Parallel	`"Free plan: 1 running loop at a time. Upgrade to unlock more."`
Browser Tabs	`1` Active Tab	Up to `6` Tabs	`"Free plan: 1 browser tab at a time. Upgrade to unlock more."`
Agent Power	Locked to Low	Low, Medium, High	`"Free plan: Agent Power is limited to Low. Upgrade to unlock Medium and High."`

Entering a valid beta key or purchasing a Pro subscription unlocks unlimited projects, multi-loop concurrency, and higher Agent Power profiles.

Next Steps

Discover how browser automation works in Browser Workers.
Review security controls in Skills and MCP.