# Studio or code?

> When to use Disko Studio, when to write code, and how to move a Studio project to code with disko eject.

|           | Studio                   | Code                        |
| --------- | ------------------------ | --------------------------- |
| You need  | a browser                | Node.js and the `disko` CLI |
| Rules are | sentences, plus scripts  | TypeScript or JavaScript    |
| Teamwork  | live, with people and AI | your own version control    |
| Testing   | Play in the tab          | `disko dev`                 |
| Limits    | the sentences on offer   | the whole game API          |

Both publish to the same registry and run in the same rooms. Not sure?
Start in the Studio.

## Move to code

`disko eject` turns a Studio project into a code project. It is one-way:
the project does not go back into the Studio.

1. In the Studio's project list, open the project's **⋯** menu and choose
   **Export**.
2. Eject it:

```sh
disko eject my-game.disko.zip
```

3. Run it and keep going in code:

```sh
cd my-game
disko dev
```

The project must have no errors. `--out <dir>` picks the folder. See the
[`eject` command](/reference/cli#disko-eject).