Importing projects

Bind an existing repo

Point a project at a codebase and the engine works against the real files — tasks read and change actual source, and the design system can be extracted from what's already there (Tailwind config, CSS variables, tokens.json).

Import a design system

One design system per project, from any of three sources: extracted read-only from your bound repo, picked from the preloaded catalog, or the Iterel Base default. See Design system.

Import knowledge

Connect Jira, Confluence, or Notion and import spaces and pages into your context as a tracked task with a receipt ("214 pages · 89 issues → context"). Everything imported becomes queryable and feeds every agent.

Existing Iterel projects

They open in the studio unchanged. Former phase outputs — research, strategy, flows, frames — become context and skill outputs; old links redirect into the studio.

Import a codebase onto the canvas

Turning an existing front-end into editable canvas frames — as opposed to binding it as the engine's working directory — is on the roadmap, not in the current release.