Get started

Available

Projects and workspaces

A cloud project can exist before a working tree. Bind a Mac workspace when you need local execution.

Open beta guideJump to first section

Start on the web

Create a scratch project or attach a GitHub repository reference. A reference provides synchronized cloud context; it is not a clone and cannot run package scripts or edit a working tree by itself.

Bind a workspace on Mac

Use Open Folder in the Mac app to attach the real local repository. Iterel records the path, default branch, and execution mode while keeping local credentials and source on the machine. New tasks can use an isolated branch and worktree so parallel work and review stay clean.

Preserve one project history

Opening the same project on Mac does not create a second project. Tasks, rounds, receipts, chats, Assets, membership, and context remain the same cloud records; the workspace is an execution attachment.

Design-system detection

When a workspace is bound, Iterel can extract tokens from Tailwind, CSS variables, or tokens.json. The repo remains the source of truth for an extracted system. Catalog systems and Iterel Base cover greenfield projects.

Existing Iterel data

Legacy projects stay readable. Historical agent:* conversations can be continued, and prior research, strategy, designs, and uploads remain available through the current context and Assets model.