Build products with Iterel

Iterel is the collaborative workspace around Claude Code, Codex, Cursor, and your product context. Turn intent into tracked work, review every change, and keep design, code, and decisions together.

Open beta guideJump to first section

Start a task

Bind a workspace, choose a Build engine, and complete the first review loop.

Open guide

Understand the loop

Learn tasks, rounds, receipts, missions, and the review contract.

Open guide

Use every device

See what runs in the cloud, on your Mac, and through a remote session.

Open guide

See every active feature

Scan the complete product surface and the boundaries between Build, Design, planning, context, and collaboration.

Open guide

Iterel is now in open beta. The shipped loop is practical: create or open a project, bind a local workspace in the Mac app, delegate a task to a Build engine, inspect the exact diff and verification receipt, then Accept or Discard it.

The product today

Build opens on the tasks home. Tasks run in isolated git worktrees through Claude Code, Codex, Cursor, and supported providers.
Design is the visual making mode. Project Map is the shared architecture section, and Whiteboard is the active structured-thinking surface for freeform work and capability-created formats.
Plan with mission PRDs, task specs, target dates, and a Triage queue for incoming requests from a link, Slack, or a Linear import.
Context holds project knowledge and powers cited answers, task prompts, and design guidance.
Memory carries accepted outcomes, decisions, rules, task/mission references, and cited evidence across engines through immutable Context Packs.
Assets holds saved documents and files. Draft capability outputs do not join project context until you explicitly save them.
Local projects include the complete offline Build loop, shared Board, Command center, rules, memory, local Assets, Preview, terminal, and explicit cloud-copy door.
Web and mobile are real clients for cloud-backed work, collaboration, and review. Machine-backed code work runs on your Mac locally or through a same-user remote session.

Control, context, and taste

Control means a task has a visible plan, full activity, exact changes, gates, and a receipt. Context means every engine receives the project knowledge and task history it needs. Taste means design-touching work is guided by the project's design system instead of generic defaults.

Product boundaries

Board owns planning, Design owns direct visual making, task Preview owns runtime inspection, and a real IDE owns deep code editing. Iterel intentionally has no duplicate Build planning canvas, permanent Code mode, browser on a Design frame, zero-machine cloud code host, or collaborator-controlled access to another person's Mac.