Loading...

The Code Studio on a Phone

Three tabs — Chat, Files and More — and a build bar that never takes you away from what you were doing.

The phone is not a small computer

The Code Studio on a phone is not the desktop editor squeezed onto a small screen. It is built around the one job a phone is actually good at: ask for something, watch it get made, and take the file away.

The bar along the top has three entries:

• Chat — the AI, where you type what you want. A project opens here.
• Files — the file tree
• More — the editor, the changes view and the tools

On plugin and mod projects the top bar also carries a Build .jar button, which reads Building… while a build runs. That is where a compile starts on a phone.

It is the same project underneath. Anything you change on your phone is there when you open the project on a computer, and the other way round.

Everything starts in Chat

A sentence or two is enough — "a plugin with /sethome and /home, one home per player, three-second warm-up that cancels if you move" beats a list of keywords.

When the AI needs an answer mid-build, the question arrives right there in the chat with the choices as buttons — one tap and the build carries on.

You can put the phone down

The generation runs on the server, not in your browser. Locking the phone, switching apps or turning it sideways does not kill it — what you lose is the view of it, and the work carries on without you.

Come back to the project and the Code Studio checks for a job that was still running and shows you where it got to, including a While you were away card listing the files that were written while you were gone. When a Generation Is Cut Off covers that in full.

What is under More

More is where the desktop half of the Code Studio went. It opens a menu:

• Editor and Changes — the file you are working on, and the green-and-red view of what the AI wrote. Changes carries a count when a turn has touched something.
• The big view your project type carries — the bot Console on a Discord bot, the Preview on a Web App or game.
• A Tools section with the same tools the desktop ⋯ menu holds — Class Builder, Dependency Manager, Generate Documentation, Organize Imports, Clean Up Template — whichever apply to your project type.
• On plugin and mod projects, Build History.

A small dot on the More tab is telling you something is in there: red when the build log has error lines in it — the fault is in the build output, not something to hunt for in your files — otherwise a quiet one meaning the last turn changed files you have not looked at.

The build bar

Pressing Build .jar does not take you anywhere. A thin strip appears above the tabs — Queued…, then Building 40%, ending in Build complete, Compile error or Build failed — so you can carry on reading or typing while it runs. Once it has finished, swipe it to the right to dismiss it. The finished jar is offered for download from the build result in chat.

Phones are best for the talking half of the work — asking for something, answering its questions, taking the file. For heavy typing across many files, open the same project on a computer; it is the identical project either way.

Where to next

• Next in Code Studio (IDE): The Smaller IDE Tools
• Nothing to open yet: Starting a New Project — Making the project this screen then builds.
• The AI asked something: Plans & Questions — The questions the AI puts in front of you mid-build.
• If your screen locked: When a Generation Is Cut Off — What to do when the phone locked mid-build.

32 of 37 in Code Studio (IDE) · Last checked 16 September 2026 · Previous: Split View