AI Agent Quickstart
Vivreal is building an AI agent system that lets you manage your content, sites, and integrations using natural language. This tutorial previews what is coming and shows you how to prepare your workspace today so you are ready when agents launch.
The agent system is currently in development. This tutorial describes planned functionality and best practices you can follow now.
What Are Vivreal Agents?
Instead of navigating menus and filling forms, you will be able to type commands like:
- "Create a new blog post titled 'Spring Sale' with a publish date of next Monday"
- "Add a price field to my Products collection"
- "Deploy my site with the ecommerce template"
Behind the scenes, a team of specialized agents handles the work.
The Six Planned Agents
Orchestrator Agent
The entry point for every request. It interprets your prompt, determines which agents are needed, and sequences multi-step workflows. For example, "Set up a blog and deploy it" would invoke the Collection Agent, then the Site Data Agent, then the Site Frontend Agent.
Collection Agent
Creates and modifies collection schemas. It can add fields, change field types, rename collections, and manage schema validation rules. It reads your existing schema before making changes to avoid conflicts.
Collection Object Agent
Handles CRUD operations on individual collection objects. It can create, update, delete, and search objects within any collection. It respects your schema — it will not invent fields that do not exist.
Site Frontend Agent
Modifies component layouts, page structures, and visual elements on your deployed site. It works by editing the Next.js code in your site's GitHub branch and triggering a rebuild.
Site Data Agent
Manages environment variables, subdomain configuration, and deployment settings. It handles the infrastructure side so the Frontend Agent can focus on code.
Integration Agent
Enables and configures integrations using the manifest system. It reads integration manifests to understand what configuration is needed, then wires the connection without hardcoding any logic.
Prepare Your Content Today
You can take several steps now to make your workspace agent-ready:
Use clear, descriptive collection names
Agents interpret your requests based on collection names. "Products" is better than "prod_v2". "Blog Posts" is better than "content_1".
Keep schemas well-defined
Add descriptions to your schema fields when possible. The agent uses field names and types to understand what data to fill in. A field named publishDate with type date is unambiguous. A field named d with type text is not.
Organize with tags
Tag your collection objects consistently. Agents can filter and search by tags, so a well-tagged catalog is much easier to work with via natural language.
One collection per concept
Avoid putting unrelated content in a single collection. A "Products" collection and a separate "Blog Posts" collection is better than a "Stuff" collection with a type field. Agents map each collection to a distinct concept.
Agents will never reference collection fields that are not in the provided schema. If you ask an agent to add content that requires a field which does not exist, it will ask you to create the field first rather than guessing.
What to Expect at Launch
- The agent UI will live at the
/app/agentroute in the portal - You will be able to chat with the Orchestrator in a sidebar panel
- Each action will show a preview before executing so you can approve or reject
- Audit logs will track every agent action for transparency
Next Steps
- Build a Product Catalog — get a well-structured collection ready
- Create a Blog — another clean collection for agents to work with
- Watch the Vivreal changelog for agent launch announcements