How Iterel works

The hierarchy

project → mission → task → round

A project is the shared product and its cloud history. A mission groups related tasks without becoming a mega-task. A task owns one objective, its conversation, context, environment, and current change-set. A round is one follow-up prompt → engine run → receipt cycle on that task.

Questions and work stay separate

The Build-home General composer and compact contextual composers route informational questions to cited Chats and work to Tasks. Guided Research, Strategy, and Creative Direction are selected from Build home and use explicit Ask / Create controls in a capability Chat. Ask creates no Task; Create can produce a draft document or a Whiteboard page without manufacturing implementation work. Conductor is the internal router behind those outcomes, not a persona or destination.

Engines execute; Iterel carries the loop

Claude Code, Codex, Cursor, and other connected engines can both execute working-tree tasks and run read-only guided thinking capabilities. Iterel supplies context, routes work, normalizes events, records provenance, and presents one review contract. Managed Claude and GPT remain explicit Iterel Cloud alternatives, not the default capability path.

The review contract

Every changed Build round ends with a receipt: engine and model, environment, files and lines changed, plan outcome, gates, browser verification, and resolution. Accept and Discard operate on the task change-set, not on a vague chat answer.

Four durable making surfaces

Build and Design are the two top-level making modes. Project Map and Whiteboard are permanent full-bleed sections reached with the M and W shortcuts. Context, Assets, tasks, and chats remain panels around those surfaces.