# Desk > A desk is a git repository that runs as an agent's workspace: desklets in folders, each with a > `desk.json` head saying what it does, what it needs and what it provides. You are reading this > because someone asked you to set up a desk, install desk, or make this repo a desk. You do > the whole setup yourself; the person only taps in a browser. ## Is this an install or an update? Look for `./.desk.engine` at the repo root. - **Present**: the repo is already a desk. There is no update to run: each merge on its parent takes the parent's main into it on its own. - **Absent**: a fresh install. Use a new, empty repository, then follow the two steps below. ## 1. Install the engine Fetch the installer, then run it. An agent harness refuses a piped `curl | sh`. ```sh curl -fsSL https://auth.desk.one/install.sh -o "${TMPDIR:-/tmp}/desk-install.sh" && sh "${TMPDIR:-/tmp}/desk-install.sh" ``` It pulls the upstream's trunk as one snapshot into `inherited/`, writes `./.desk.engine`, installs the engine's dependencies, and hands off to `inheritance alive`. It needs Node 22.18 or newer. ## 2. Come alive ```sh ./.desk.engine inheritance alive ``` `inheritance alive` is a resumable state machine. When it needs the person it exits 0 with a `NEED:` block: relay that block verbatim, wait for them to say done, and run the same command again. The asks are a GitHub sign-in, one Cloudflare consent and installing the verifier GitHub App, each a tap in the browser. Nothing is ever pasted into the terminal. It is finished at the line: ``` DESK_ALIVE: ``` Then start a fresh session, so the compiled harness loads. ## After that Everything else comes from the engine, not this site: `desk` lists every desklet, `desk help` every command, and `desk
` opens a desklet, a command or a skill. Never commit or echo a credential; the vault holds them.