XOne Agent
XOne Agent is an AI agent that is an expert on XOne, the platform for building native mobile apps for Android and iOS. It answers questions by consulting the XOne reference documentation and, connected to your XOne WebStudio account, works directly on your CloudStudio project: it analyses it, programs changes, fixes errors and tests on the device.
Inside, an orchestrator takes each request and shares it out among specialists: a development manager that plans the work, a JavaScript expert, an XOne XML and CSS expert, a project analyser, a device tester and a visual designer.
There is a newer version, XOne AgentV2, which plans and verifies each task before delivering it.
When to use it
- A developer wants to ask how something is done in XOne without searching the documentation.
- You want the agent to add a screen or a field to your XOne app.
- You need to find and fix a project’s build errors.
- You want an analysis of an inherited project before you start working on it.
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 talks to you and shares out the work. |
| User Prompt | The user’s request. Default: {input}, the message that comes from the chat. |
| CloudStudio Email | The email of your CloudStudio user. The agent works on your behalf as that user. |
| CloudStudio Project | The project opened at the start. Optional. |
| Execution Mode | direct: the agent carries out changes as soon as you ask. planner: it first shows you the plan and waits for your confirmation. Default: direct. |
| Developer Model | Optional connector for a model that is good at programming, used by the JavaScript and the XML and CSS experts. If you don’t connect it, the Model one is used. |
| Fast Model | Optional connector for a lightweight model that routes requests and summarises screenshots and analyses. If you don’t connect it, the Model one is used. |
| Embeddings | Optional connector for the embeddings model used to search the XOne documentation. |
| Tools | Optional connector to give the agent extra tools. |
| Input Token (NOT USED) | Has no effect: the agent gets its CloudStudio access from the credential and the session’s email on every run. It is kept only so existing flows keep their field. |
Specialist instructions
The Development and Specialists tabs of the settings panel hold each specialist’s instructions: Dev Manager, JS Expert, XML/CSS Expert, Project Analyzer, Device Tester and Visual Designer. They come ready; change them only if you want to adjust how one of them works.
Advanced options
| Field | What it does |
|---|---|
| MCP Tool Profile | The group of CloudStudio tools that are loaded: all, developer (collections and scripts), designer (layout and CSS), project (access and branches) or none. Default: all. |
| Documentation Mode | How the agent consults the XOne documentation. Its only option is rag, search by meaning. |
| 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. |
| Max Iterations | Maximum number of steps the agent can take for one answer. Default: 35. |
Output
The Response output is the agent’s answer: the explanation it gives you or the summary of the changes it made to the project. 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 development team wants an XOne assistant in its internal chat.
- Add a chat input component and connect it to User Prompt.
- Connect a model component to Model.
- In Credential pick the team’s XOne WebStudio credential and in CloudStudio Email write the developer’s email.
- Set Execution Mode to
plannerto review each plan before the agent touches the project. - Connect Response to the chat output and ask, for example, “Add a phone field to the customer form”.
Good practices
- Start with Execution Mode set to
planneruntil you know how the agent works with your project. - Turn on Use memory so the agent remembers what you discussed and the work in progress.
Related components
- XOne AgentV2: the newer version, with plan approval and verification in the simulator.