Documentation

Getting started

Sign in, then create a project from the dashboard. Each project boots its own Node.js container in your browser — nothing is installed on your machine. Open the terminal and run npm install && npm run dev to start the dev server; the preview tab picks it up automatically.

The AI agent

The agent panel sits on the right of the editor. It can list, read, write, rename and delete files, and run commands in your container. It sees your project's file list and whichever file you have open, so "add a health check to the server" is enough context.

Deleting files and running commands ask for your approval first — the tool call pauses with Allow and Decline buttons. Everything else runs immediately and shows you the input and result.

Inline AI

Pause while typing and the agent suggests a continuation in grey. Press Tab to accept it or Escape to dismiss it. Press Ctrl+I to describe a change in words instead: with code selected it rewrites the selection, otherwise it inserts at the cursor. You see the proposed code and choose whether to apply it.

Collaboration

Open the chat panel and share your project link. A room holds two people. You will see each other's cursors and edits live — concurrent changes are merged rather than overwriting each other.

The same panel carries text chat, a voice and video call, and direct file transfer between the two browsers. Calls start only when you press Call, so nothing touches your camera or microphone until you ask it to.

Exporting to GitHub

Export To GitHub creates a repository and pushes your project as a single commit. Repositories are created private by default; there is a toggle if you want it public. You will need a GitHub token with Administration: Write and Contents: Write — prefer a fine-grained token scoped as narrowly as you can.

Keyboard shortcuts

Limits

• Five projects per account.
• Two people per collaboration room.
• Your container runs in the browser tab. Closing it stops the dev server; your files are saved, installed packages are not.
• Binary files are skipped when exporting to GitHub.