Describe the business, audience, products, goals and agent rules once per project. Connected agents can read that context before interpreting your search data or saving a report.
Five explicit fields · Project-scoped · Read and write permissions
Acme · Fictional sample project
Project guidance
Shared input for this project and connected agents.
Sample states only. These controls do not run research or contact a provider.
Record what you sell, who it serves and the goals you are working toward. Keep factual guidance separate from unverified performance claims.
Use Agent rules to explain how you want evidence handled and when approval is needed. Keep credentials in the provider settings, outside these text fields.
An agent can fetch the saved context through REST or MCP and include it in an analysis. The saved update time helps it state which context it used.
The same five fields are available in the app and through the API. They describe the project without inventing facts about its performance.
No. Saving context records the project's guidance. Research execution and future tracking generation are separate actions.
No. Agents have a context read operation available, but their workflow must call it. Review the agent's instructions and saved report provenance.
Read access permits inspection. Updating context requires project write access, enforced on the server as well as in the UI.
Read the workflow guide, then use the same project context and saved results across the app and connected agents.