Projects and workspaces

Agent Teams build and run multi-agent work. Product Plans shape requirements and delivery. Architecture maps technical systems. They can live in one project without being forced into one editor.

• Use Agent Teams for repeatable work and automation.
• Use Product Plans for scope, decisions, and delivery sequencing.
• Use Architecture for system boundaries, dependencies, and technical review.

Project rows summarize child counts and recent activity. Expand a project to open a specific team, board, architecture, or run without first loading the parent editor.

Right-click an Architecture component to inspect, build, duplicate, copy, or remove it, and right-click open canvas space to add a service, database, or external API. Product Plans use the same pattern for card actions and for adding features, screens, milestones, or requirements.

Escape closes the active guide, dialog, or menu without clearing the Architecture. Starting a new Architecture remains an explicit New command. An untouched or successfully saved canvas can leave the page without an unnecessary browser warning.

Keep source material close to the project, but connect it only to the Agent Team cards that need it. Smaller context is cheaper, easier to audit, and less likely to leak unrelated information into a run.