Product

The Product page is where you write down what you're building and who it's for. It holds the stable, high-level context behind a project, the part that rarely changes while tasks and releases churn underneath it.

You don't need it to start shipping. But filling it in keeps releases, AI suggestions, and your agent pointed at the same goal.

Product stage

Every project has a stage that says where the product is in its lifecycle:

• Idea, shaping the concept, audience, and reason to build before locking in scope.
• MVP, building the smallest useful version and proving the core workflow works.
• Launched, the product is live; the focus is reliability, feedback, and the next release.
• Growth, improving acquisition, retention, and the systems that help it scale.

The stage shows as a rail at the top of the page so you can see progress at a glance. Move through the stages as the product matures, it's a property of the project, not a one-way gate.

Stage also shapes Auto project setup: the AI tailors the areas, releases, and tasks it proposes to where you actually are. An idea-stage project gets a critical-path MVP backlog; a growth-stage project gets activation and retention work instead of scaffolding.

Project context

Four short fields capture the product itself:

• One-line description, a plain-English sentence explaining what this product is.
• Target user, the specific person or team it's built for.
• Problem to solve, the core pain the product exists to fix.
• Why this wins, the advantage, insight, or wedge that makes it worth building.

Keep them sharp rather than exhaustive. They're prompts to force clarity, not a spec.

Agent context

The Agent context field is for stable product context an AI coding agent should remember across tasks, the things you'd otherwise repeat in every prompt: the stack, conventions, constraints, or domain rules that don't change task to task.

When an agent connects through the plugin or MCP server, this context travels with the project so suggestions stay aligned without you re-explaining the basics each session.

Editing and permissions

The project owner can edit every field inline, click a field, type, and save. Other project members see the Product page as read-only.

Edits sync to every connected session in real time, the same as the rest of the project.