Prophecy agents operate within your selected deployment environment and respects existing access controls. The agents are assistive rather than autonomous: they do not have autonomy to connect to external systems or perform any action without approval. Prophecy agents are considered limited risk according to the EU AI Act. This page explains how data is accessed, executed, and stored when using agents.Documentation Index
Fetch the complete documentation index at: https://docs.prophecy.ai/llms.txt
Use this file to discover all available pages before exploring further.
Key principles
- Agents generate transformation logic and suggestions, but you review and approve all changes before pipelines are run in production.
- Agents operate only within your Prophecy deployment and connected data platforms.
- You can inspect all generated transformations in visual, SQL, or documentation form before execution.
- You maintain full control over whether changes are applied.
Storage and environment
Agents run inside your Prophecy deployment environment. Prophecy stores:- Agent chat history.
- Project metadata (pipelines, analyses, schemas, configurations).
- Version-controlled project artifacts.
LLM interaction
When generating suggestions, agents may include project metadata in prompts sent to the configured language model. This metadata may include:- Table and column names
- Schemas and data types
- Transformation code within the current project

