Explain the product once
Open Project context in the sidebar. On mobile, choose More in the bottom navigation, then Project context. Project-team roles can read it; owners and admins can edit it.
Open the project dropdown and choose Your projects. On the relevant card, choose Project context. The context dialog shows the project’s name and keeps you in Your projects. Owners and admins can edit context. Product managers and developers can read it; testers and client reviewers do not have this control.
During Project setup, choose Add project context or Review project context. The dialog keeps your setup page open. Saving context or closing the dialog returns you to the same setup step so you can continue installation.
Save the product’s purpose, audience, important journeys, constraints and any terminology that helps Astor understand it. Context belongs to this project; it is not a global description of every project in your account.
Approved knowledge opens by default. When a review is not in progress, Still to clarify shows unresolved points without opening a history section. You can fold the approved details when you need more room.
For example, describe who buys the product, what they are trying to accomplish and what a successful checkout should show. This helps Astor ask fewer repetitive questions when reviewing feedback.
Add context manually
Choose Add manually or Edit knowledge. In Edit project context, review the fields and choose Save knowledge. Manual editing uses no capacity. Keep context factual and update it when your product changes.
Opening Project context does not start new AI work. If a website review is already running, its progress can continue; otherwise you choose when to start research.
Learn from the website
When website research is available, choose the website and review the quoted cost before starting. The review includes the website check, necessary follow-up questions and a proposed update. Research can start before script installation.
The proposal does not replace approved context automatically. Read it, answer any relevant questions and approve the fields you want to save. If AI is unavailable or the project has insufficient capacity, you can still edit manually and continue installation.
If processing is interrupted, approved context stays unchanged and that attempt’s reserved capacity is returned. Review the current job before retrying. A late reply from the interrupted attempt cannot replace a newer result; manual editing remains available.
For an unfinished website review, Saved answers shows the answers already recorded, including after a failed, cancelled or outdated review. Read them before editing context manually. Displaying these answers does not approve a proposal, start another AI job or use more capacity. A review with no recorded answers shows no empty section.
In Clarify project context, answer the current question directly. Completed clarifications holds earlier answers separately; open it when you need them. Distinct context remains visible, while an introduction that exactly repeats the current question appears only once. Closing with Save for later keeps the stored proposal and answers without approving them.
If access ends while a review is updating, the earlier private view and edit controls are removed. An ended sign-in returns you to sign-in. A role that still allows reading keeps approved context visible, but closes the editor and refreshes project permissions. A temporary connection error keeps your context and manual editor available while Astor reconnects; it does not start another AI job.
Resolve what is still unclear
Still to clarify appears above Approved knowledge. Review these questions first. Answer only what you know; uncertain facts should remain open instead of becoming assumptions.
Follow-up questions use a conversation: choose a suggested answer or write your own, one question at a time. Earlier answers remain visible and are saved as you go. If sending fails, your answer stays available to retry. Choose Continue with what Astor knows when you want to review the proposal without answering everything.
Saved context helps clarification, ticket reviews and agent work. It is background information about the product, not proof that a particular tester action or business outcome happened.