# Working from another computer

Your app's code lives here, with every version. No git required.

You built an app with your AI on one computer. Now you are on another, and the AI there has never seen the project. Normally this is where people learn about git. You don't have to.

## The two steps

Sign this computer in:

```bash
npx uarpie login
```

It shows a short code and opens your browser. Sign in (by email, as always) and tap **Approve this computer**. Once per computer.

Then bring the app's code here:

```bash
npx uarpie clone family-books
```

The live version's source lands in a folder named after the app, together with its `deploy.json`. Make changes with your AI, then deploy from that folder as usual. It is the same app; the next deploy is simply the next version.

## Or just tell your AI

> Clone my family-books app from uarpie and continue where I left off.

Your AI runs the sign-in, shows you the link to approve, clones the app, and carries on.

## What comes along, and what doesn't

- The source of the version you choose (the live one by default; `--version 12` for an older one).
- `deploy.json`, so the platform knows it is the same app.
- **Not** your secrets. They stay on the platform and keep working on the next deploy.
- **Not** the database. It lives on the platform too; there is nothing to move.

## Where does the code live, then?

Every deploy stores the exact source that went live, alongside the built app. You can download it from the app's **Settings** tab at any time. That store is your version control: numbered, dated, and restorable. If you *do* use git, nothing changes: when a repository exists, each version also records the commit it came from.

## Other computers signed in

Under **Settings** in your dashboard you can see every computer that has been approved and remove one.