XOne AgentV2
XOne AgentV2 is the new version of the AI agent that is an expert on XOne, the platform for building native mobile apps for Android and iOS. It answers questions about the XOne documentation and about your open project, plans development tasks and checks each one with the XOne simulator before uploading it to CloudStudio.
Every message is classified first: a question about XOne, a question about the project, a development task, or a query that needs information from outside XOne, such as how to integrate another service’s API. For development tasks the agent writes a plan; for the more complex ones it shows you the plan for approval. Then it carries it out and a reviewer checks that what the plan said was done.
It lives alongside the first version, XOne Agent: flows that already use it don’t change.
When to use it
- You want the agent to build a feature in your project, but reviewing the work plan first.
- A developer asks how part of their project or of the XOne documentation works.
- You need to integrate your app with another service’s API and want the agent to research how.
- You want every change tested in the simulator, or on the real CloudStudio device, before it is accepted.
- You need the agent to generate icons for the app.
Configuration
You need an XOne WebStudio credential with the CloudStudio access details XOne gives you. See Credentials.
| Field | What it does |
|---|---|
| Credential (required) | The XOne WebStudio credential the agent uses to access CloudStudio. |
| Model (required) | Connector for the main language model, the one that answers and does most of the work. |
| User Prompt | The user’s request. Default: {input}, the message that comes from the chat. |
| CloudStudio Project | The XOne project the agent works on. Always fill it in: the agent never works outside a project and, without it, the message fails. |
| CloudStudio Email | The email of your CloudStudio user. The agent works on your behalf as that user and keeps its long-term memory for them. |
| Fast Model | Optional connector for a lightweight model used only by the XOne documentation specialist, the one that makes the most queries. If you don’t connect it, the Model one is used. |
| Developer Model | Optional connector for the model that programs the changes in the project. If you don’t connect it, the Model one is used. |
| Planner Model | Optional connector for the model that writes the plan and splits it into tasks. If you don’t connect it, the Model one is used. |
| Vision Model | Optional connector for a model that can read images, which compares built screens and generated icons with their design. |
| Tools (executor) | Optional connector to give extra tools to the part that edits the project. |
| Web Search | Optional connector for a web search component. The agent uses it when the answer lies outside XOne. |
Prompts and Development tabs
- The Prompts tab holds the instructions of each part of the agent, for example Voice Prompt (responder), which writes the reply you read, or Planner Prompt (task breakdown), which splits the work into tasks. They come ready; change them only if you want to adjust how one of them works.
- The Development tab holds the Sandbox connector: connect a sandbox component so the agent can generate icons in SVG, PNG or JPG. Without it the agent works the same but does not generate images, and tells you so.
Advanced options
| Field | What it does |
|---|---|
| Auto-approve plans | When on, the agent carries out plans without asking for your approval. Use it only in flows with no person on the other side. Off by default. |
| Auto-resume unfinished work | What happens if a new request arrives while an earlier plan has work pending. Off, the agent asks you; on, it carries on with the earlier work without asking and leaves the new request for later. Off by default. |
| Test on the real device (live-simulator) | When on, before accepting a task the agent tests it on the real CloudStudio device: it uploads the changes, opens the app and walks through the screen. It is slower. Off by default. |
| Live-simulator navigation route | The path to the screen being tested, in one line with steps separated by →, for example pulsa "Carrito" → espera "Listado". The possible steps are pulsa "Texto", rellena "Campo" = "valor", espera "Texto" and tecla BACK or tecla ENTER. Empty, only the start screen is tested. |
| Live-simulator login user | The user to log in to the app if the path goes through a login screen. Stored hidden. |
| Live-simulator login password | That user’s password. Stored hidden. |
| Use memory | When on, the agent remembers the conversation between messages. Off by default. |
| Stream | When on, the answer is shown as it is written. Off by default. |
Output
The Response output is the agent’s answer: the explanation, the plan it proposes for approval, or the summary of what it did and checked. When the agent needs your approval or a decision, the message ends there and waits for your reply in the chat. Connect it to the chat output.
The Agent output delivers the agent itself, to connect it to another component that directs it. When you connect one of the two outputs, the other is hidden.
Example
A team wants the agent to develop on its ordering app with prior review.
- Add a chat input component and connect it to User Prompt.
- Connect a model component to Model and, if you want a more careful plan, a more capable one to Planner Model.
- In Credential pick the XOne WebStudio credential, in CloudStudio Project write the project name and in CloudStudio Email the developer’s email.
- Turn on Use memory so the agent remembers the plan between messages.
- Connect Response to the chat output and ask “Add a button to empty the cart”. Review the plan it proposes and approve it.
Good practices
- Leave Auto-approve plans off in chat flows: reviewing the plan is the best way to avoid changes you didn’t want.
- Turn on Test on the real device (live-simulator) only for the tasks that need it, because it makes each task longer.
- Connect a Web Search if your team often asks about integrations with other services.
Related components
- XOne Agent: the first version of the agent.