Project context

Project context is what an agent reads before it works on a project: what the business is, who it competes with, and which pages matter. The assistant, the onboarding strategist and any agent connected over the MCP server all read it. Open it from Project settings, then Context.

The four sections

Section	What to write
Business overview	What the business sells, to whom, and where.
Current goal	The one outcome this project works toward now.
Positioning	How the business differs from its competitors.
Writing preferences	Tone, terms to use and terms to avoid.

Each section holds up to 20,000 characters. Write it yourself, or ask for an AI draft built from the project’s name, domain and competitors, then edit it. A draft holds up to 12 credits and is charged for the model call it makes, usually a fraction of that.

Competitors

List the domains you compete with, each with an optional name and up to 2,000 characters of notes. AI visibility compares the project against up to nine of them, and the assistant reads the list when it compares.

Key pages

Mark the pages that matter and give each a role:

Role	Meaning
hub	A page that gathers a topic and links out to the pages under it.
spoke	A page that covers one part of a hub’s topic.
money	A page that converts: pricing, sign-up, product.
other	Anything that matters for another reason.

A key page also takes a topic of up to 120 characters and notes of up to 2,000.

Research log

The research log records what was learned about the project, newest first, and shows whether each entry came from you or from an agent. Entries are appended and never edited, so the record stays trustworthy. Each entry is a summary of up to 4,000 characters.

Owners and admins edit context. Everyone in the workspace reads it, and an archived project’s context stays readable.