Skip to content

XU Code

A cloud coding environment: connect a repository and the coding agent builds against it.

Open XU Code
Checked against the dashboard on November 19, 2026

XU Code is a Xucode project: a coding workspace in the cloud. You connect a git repository, describe what you want changed, and Xuda's coding agent makes the change on a machine of its own. Before you are shown anything, the change goes through your own install, typecheck, tests and build. You see it running in a live preview, and it comes back to you as a branch you can open a pull request from.

It is something you create, like a website or a server, not a module you switch on. Every Xucode project has its own machine, and you can have as many projects as you like. Opening one opens the workspace itself, not a list of cards.

Start a project

Create it

Open the Create menu and choose Xucode in the Build & host group. The row opens for every account. A crown on it means your membership is below the one Xucode needs, and the plan is checked when you press Create (see "What it needs" below).

Connect a repository

Paste the https address of a GitHub or GitLab repository and an access token that can read it and push a branch. Press Test: Xuda reads the repository and tries a push that writes nothing. The step does not pass until both have worked, so a project never starts with a token that cannot push. Press Show me how if you have not made a token before: the guide shows each click on GitHub or GitLab and puts what you paste straight into the form.

Choose the server strength

Pick how hard the project will work: one of four sizes named Standard, Optimize, Performance and High loads, each with its disk and its price a month. You can move to another size later, and nothing on the machine is lost.

Name it

The name is filled in from the repository and is what the project is called in your dashboard. Press Create. The project opens on its workspace.

The frame these steps sit in (the rail, Previous, Next, Create and the price) is the one every create flow uses: see the create steps of Deployments.

Common jobs

Ask for a change

Type what you want in the conversation in the middle of the workspace. The agent works on a new branch off your default branch and never commits to the default branch itself. When the turn ends, the Run tab shows what it did.

Check what it did

The run panel lists the files it changed, with a diff for each, the commands it ran, and what your own checks said, including any automatic fixes it made to get them passing. Revert puts one file back as it was.

See it running

The Preview tab frames your project's own dev server. If the machine is asleep it says so and wakes on your next message.

Commit, push and open a pull request

Nothing is committed on its own. In the run panel's repository box press Commit, then Push, then Open PR.

See which branches still need a push

Press Branches in the header. A badge on it counts the branches with work that is not pushed yet, and the window lists each branch with its last commit.

Choose the models

The model menu in the conversation's strip lets Xuda pick the cheapest model that can do each request, pool a few for it to choose from, fix one, or ask two models and show where they disagree.

Change the repository

Press the repository button in the header. The window tests the new repository before it replaces the old one, and the same button saves a new token for the same repository.

Resize or switch off the machine

Press Machine. The window shows its size and its IPv6 address, and holds the same Usage, Power, Resize and Backups a server has.

Share the project

Press Team in the header. It opens the project's Team page, where you share it the same way you share a server.

What the workspace shows

The header holds the project name, the repository, Branches, Team and Machine. Under it are three panes, left to right, whatever the language of the dashboard:

  • Left: the list of sessions, each a dot and a title (amber while it is working, grey when it has finished), with New session inside it. A second tab, the working tree, lists the files that changed on the machine. It never reads on its own, because reading wakes the machine.
  • Middle: the conversation. It is the same chat as AI Chats, with the model menu in its composer strip.
  • Right: three tabs. Preview is the project running, Run is what the open session did, and Requests is every request ever made against the project, with whether it is processing, done or failed and, on hover, who asked, when, how long it took and which model answered.

Drag the lines between the panes to resize them. Dragged narrow, the left and right panes fold to a strip of icons instead of disappearing, and the layout is remembered in your browser. Below 1024 pixels the sessions list is hidden and a switch at the foot chooses between the chat and the right pane.

Until a repository is connected, the panes are not drawn at all. The workspace asks for a repository instead, and the connect window opens by itself the first time. Closing it leaves you on that page.

A code chat can also open on its own screen, with the conversation on one side and the run on the other. That is the code chat, reached from the project a chat belongs to.

What it needs

Xucode is included with Pro membership and above. An account below Pro sees a crown on the Create menu row. The row still opens, and the refusal comes when you press Create, saying Xucode is included with Pro and above and asking you to upgrade your membership.

Two things are billed separately from the membership, and this page does not quote their amounts:

  • The machine. Every project has its own, in the size you chose. Each size card shows its price a month, and the create footer shows the total before you press Create. Resizing later changes the size you are billed for.
  • The AI work. The engine says what it runs on. An engine on Xuda's key uses your AI credits, and an engine on your own provider key uses none. If you pick an engine that needs a key you have not added, you are taken to the workspace's hosting settings to add it. See AI credits.

Where to find a control

Every button, field and tab of the workspace and of the windows it opens is in the Dashboard Manual, screen by screen, with what it does, when it shows and a link that opens the dashboard on it.

How is this guide?

Last updated on November 15, 2026