A brief becomes a real page.Help your AI remember the site
Set site context and approve useful memory for later sessions.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- A verified connection and a practice site.
- Pro and Project Memory enabled for memory features.
Let’s do this, step by step.
Step 01
Fill in the site profile
Open Build → Context. Enter business name, industry, site purpose and Brand voice. Add concise Extra instructions for rules used in every session.
Tell the AI what the business does and how it should write. Keep permanent guidance short and factual. Put task-specific details in the task prompt.
Step 02
Choose detected information
Review Detected switches for builder, theme, global styles, structure and plugins. Use Refresh after site changes. Check Context size against the 8k guide.
Choose the site information useful to your agent. Refresh it after changing the site. The size indicator is a guide, so remove repeated instructions rather than filling it.
Step 03
Preview, save and reconnect
Use Preview what the AI sees. Keep Send context to connected agents on for profile and extra instructions. Choose Save context or Save changes, then reconnect.
Preview the exact text the agent will receive. The preview includes unsaved edits, so save before reconnecting. The send switch controls your profile and extra instructions; detected information has its own switches.
Step 04
Propose and review memory
With Pro and Project Memory on, ask for one durable fact. Open Build → Memory → Pending review, inspect it, then approve or reject. Leave Require approval on in Settings.
Memory is guidance learned during work. A proposal stays pending until you approve it. Review its facts before letting future sessions use it.
Step 05
Maintain active guidance
In Active guidance, edit or switch off outdated items. Add a manual Guardrail, Site fact or Convention only when ready for it to become active immediately.
Turn off guidance that is no longer true. Manual additions become active straight away. An instruction only blocks an action when it has an approved, supported enforcement target.
Step 06
Review session summaries
Use Session history to inspect summaries. In Settings, Auto-summarize sessions is optional and off by default; enabling it uses model tokens. Check guidance in a fresh connection.
Session history helps you pick up later. Automatic summaries can use your model allowance or paid tokens. Turn them on only if you want them, then check what a fresh session remembers.
You’re done when…
A new session can recall the approved fact, and you know how to remove it.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.