

The main window is divided into functional areas:
The Dashboard provides a bird's-eye, real-time view of the health of your agent ecosystem. It consolidates critical metrics so you can proactively monitor efficiency and operational performance.
On the Dashboard, you will find fundamental indicators such as:
This option allows you to create the basic structure of a LangGraph agent from scratch or integrate Curator with existing code. By selecting a folder that already contains a LangGraph project, Curator acts as an RPA robot, providing the execution interface, log monitoring, and graph visualization for your external code.
Ctrl + N)After creation, you will have access to the detailed project settings, where you can define specific execution parameters and behavior for your agent.
Curator includes specialized templates for PDF processing with AI, or custom RPA robot on a solid and scalable structure:
| Template | Description |
|---|---|
| Reframework PDF Batch | Processes multiple PDFs from a folder with a single prompt. |
| Reframework Excel Batch | Processes multiple Excel files from a folder, the user defines which columns contain information about document paths and prompts that will be used to process the documents |
| Reframework Base | Base architecture created so the developer can build a custom RPA robot on a solid and scalable structure. |
For PDF agents, you can modify the prompt, model, validation, and columns.
Start the execution and follow the logs in real-time on the Execution tab.
| Button | Description |
|---|---|
| ▶️ Run | Starts agent execution. |
| ⏸️ Pause | Temporarily pauses execution. |
| ⏹️ Stop | Completely stops execution. |
Analyze the structure and flow of your agent dynamically on the Visualization tab.
The main highlight of this tab is the ability to track the flow in real-time. Through fluid animations, Curator highlights exactly which node or step the agent is processing at that moment, allowing unprecedented observability over your LangGraph code execution.
The Jobs section is the heart of Curator's monitoring. This is where records of all executions performed by your agents are stored. You can track the progress of each task and access the complete interaction history.
Each Job has a status that indicates the operation's result:
| Status | Description |
|---|---|
| Success | Execution was successfully completed. |
| Cancelled | Execution was interrupted by the user. |
| Info | Informational status about the process progress. |
| Failed | A critical error occurred that prevented completion. |
Triggers allow you to automate the triggering of your agents based on external events or time schedules. With them, your agent no longer depends on manual execution and starts operating autonomously.
You can configure different types of triggers, such as Webhooks for integration with other systems, or Schedules (CRON) for tasks that should occur at regular intervals.
In the configuration interface, you define the activation rules, the input parameters that the trigger will send to the agent, and monitor the firing history of each trigger.
The Logs tab maintains a complete history of all executions, allowing filtering by project, text search, and export.
| Status | Meaning |
|---|---|
| INFO | Normal processing event |
| WARNING | Attention, but not critical |
| ERROR | Something went wrong |
| SUCCESS | Operation completed successfully |
One of the most powerful features of PYE Agent Curator's standardized agents is the intelligent validation system. This mechanism ensures the reliability and accuracy of responses generated by AI models, offering two distinct verification modalities.
Validation is especially critical in scenarios where the accuracy of extracted or analyzed data can impact business decisions, regulatory compliance, or downstream automated processes.
Exact Double Validation is a deterministic method that compares responses from two different AI models using literal string matching. This method is ideal for structured data extraction where the expected response is objective and does not allow variations.
Subjective Double Validation uses a third-instance AI approach to evaluate semantic consistency between two responses. This method is suitable for analyses involving interpretation, summarization, or extraction of complex concepts.
| Aspect | EXACT Validation | SUBJECTIVE Validation |
|---|---|---|
| API Calls | 2 (both models) | 3 (models + validator) |
| Speed | ⚡ Faster | 🐢 Slower |
| Cost | 💰 Lower | 💰💰 Higher |
| Response Type | Objective and structured | Interpretive and contextual |
| Criterion | Literal equality | Semantic consistency |
| Best For | Structured data | Complex analyses |
When a transaction is marked with a yellow row, it indicates that validation detected inconsistencies. In this case, it is recommended to: