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.

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.