Cloud workspaces
for your coding agents.

Run your coding tools on a server QIOI manages. Open the same project files and terminal sessions from another computer’s browser.

Illustration of two desks connected to the same workspace server by a green path.

Where your work runs

Your browser gives you access to the workspace. The workspace server holds your project and runs your tools. Your AI account supplies the models those tools use.

Your browserOpen Console, then Desk
QIOI workspaceProject files and running terminals
Your AI providerModel access through your account

A home for
your AI agents.
Open anywhere.

Try the browser Desk. Switch from launchpad to notes, start a different example tool, or open the Files tab to see what’s in the project.

QIOI DESKINTERACTIVE EXAMPLE
console.qioi.io / workspace
QIOIPersonal workspace
Demo workspace
/workspace/launchpadsaved session
✳
Claude CodeYour tools. Your own account.
❯Let's build the next thing.
●

Ready when you are. Your project is right here.

▾ launchpad/├── src/├── public/└── README.md
❯Your next idea starts here
Example session
Coding toolsClaude CodeCodexOpenCode

Available tools vary by workspace.

Your work keeps its place.

Close your laptop.
Keep your place.

A running shell can continue after the browser closes.

Try reconnecting

Your tools.
Your own accounts.

Use your own subscription or API key. Your AI provider bills model usage separately.

Another computer.
The same project.

Sign in from a different computer. Your saved files are already in the workspace.

Your project is a folder on the server

Open a project to give your shell and coding tool the same working directory. When you switch tools, open the same folder to pick up the files and changes you’ve already made.

Each tool keeps its own conversation history. Save decisions in a project file such as the README so the next tool can read them. Use Git to keep a copy of changes outside the workspace.

Browse the example files
Example projectlaunchpad/
  • README.mdSetup, commands, and project decisions
  • src/Application source code
  • tests/Checks to run before committing

From Console to your first session

Follow the path from your workspace list to a project and its terminal. Select a step to see the example.

Console My workspaces
Personal workspace

The workspace list shows what your account can open.

Come back to the same terminal

Your terminal runs on the workspace server. Close the browser and a running session can continue while the workspace is online. Sign in again to return to it, including from another computer.

Closing a browser and restarting a server have different effects. A restart ends running processes. Saved files remain available.

Connection example Workspace online
Laptop browserConnected
launchpad / shell
$ npm run dev
Listening on port 3000

The browser is connected to the project shell.

What you can do from Desk

Review a change

Ask an agent to investigate a bug in one terminal, then open a second shell in the same project to inspect its diff and run your tests before committing.

git diff

Investigate a failing test

Run the failing test in a shell. Give your coding tool the exact error and ask it to trace the failure to a specific file before changing anything.

npm test

Check a build

Run the project’s build command and inspect its output in the shell. Fix any errors in your workspace before publishing through your usual deployment service.

npm run build

What QIOI manages

With your own VPS, you set up its server and decide how to reach it. A QIOI workspace comes with a managed server, an account Console, and a browser Desk.

Workspace server
QIOI provides and hosts the environment where your projects and coding tools run.
Account access
Console shows the workspaces assigned to your account and gives you a place to open them.
Browser Desk
Open your project’s shell and files from a browser without setting up an SSH client on that computer.

Workspace questions

Do I need to install anything on my computer?

For browser access, open Console and launch Desk. Your shell and coding tools run on the workspace server.

Can I use more than one coding tool?

You can open separate terminal sessions and use the tools available on your workspace. Each tool has its own account setup and conversation history.

Can an agent keep working while I’m away?

A running tool can continue after you close your browser. It may pause for approval, finish the task, or hit a provider limit. A server restart ends running processes.

Do my local folders sync automatically?

Desk opens the files stored on the server. Bring the project into your workspace first, for example by cloning its Git repository. Use your usual Git workflow or keep a separate copy of important files.

Can I use a private Git repository?

If you can access the repository from the workspace, use your Git host’s supported authentication to clone it. Its access rules still apply. Keep credentials out of project files and agent prompts.

Can I publish a website from Desk?

Desk is for development. For a public release, use your project’s usual deployment workflow and hosting service.

How do I get a workspace?

Existing customers can sign in and open their assigned workspaces. New workspace registration is currently closed.

Your next idea.
A place to begin.

Open your workspace and pick up your work.

Sign in to your workspace