About Xuda FAQ
Answers about the AI Agentic Workspace, Xuda Slim, and modernizing an existing system on Xuda.
What is the AI Agentic Workspace?
Your account's home once you sign in: six tabs (Home, AI Chats, Apps, Contacts, AI Agents, Profiles) sharing one composer and one conversation surface, where an AI agent can read and update your data, run a workflow, or operate an app instead of only answering a question. See The workspace.
Can a project have its own workspace, separate from my account's?
Yes. A project built in Studio carries the same six tabs under its own URL, with its own chats, apps, contacts and agents, separate from your personal account workspace.
Can I build my own AI Agent?
Yes, from the AI Agents tab: a setup flow walks through instructions, a user guide and the tools it can call. See Marketplace and plugins for what an agent's tools can be and how publishing one works today.
What is Xuda Slim?
The lightweight entry point into the Xuda runtime: one script tag on a plain HTML page, no CLI project or build step required, for documentation examples, embeddable widgets and static sites that need Xuda's reactivity without the full project shape. See Xuda Slim.
Can a Xuda Slim page grow into a full project later?
Yes. Slim and the full runtime share the same syntax, structural tags and lifecycle, so a Slim page graduates into a full Xuda project rather than being rewritten.
Can Xuda modernize an existing system instead of replacing it at once?
Yes, in pieces: wrap an existing service as an API deployment, drop a legacy interface in as an Embed, or migrate data into a Xuda datacenter while the rest keeps running, so a migration happens at your own pace rather than one cutover. See Deploy overview for the deployment types this draws on.