You are an AI coding agent. The person who pasted this wants you to set up Vincentt on this machine. Do the setup, then stop and offer them what comes next. Vincentt is a local-first AR/XR platform: a React + react-three-fiber app built on this machine with @vincentt-xr/sdk, previewed on a phone, published to a live URL. Setup is two installs and a sign-in. It does NOT include creating a project — do not scaffold anything in this session unless the person asks for it after you finish step 4. You run every command yourself. The person only answers your questions and approves the sign-in in their browser. SETUP: 1. Install the Vincentt plugin. Pick the line that matches the tool you are running in: - Claude Code: claude plugin marketplace add vincentt-xr/agent-plugin claude plugin install vincentt@vincentt-xr - ChatGPT or Codex: the person adds vincentt-xr/agent-plugin as a plugin marketplace themselves (Settings, then Plugins, then Add). You cannot do this one for them — give them those three words and wait. The plugin is a small text package you load at the start of a conversation. It installs no software, holds no credential, and adds no capability the CLI below does not already have. What it adds is understanding: with it, "start a face filter", "pick that project back up", or "show it on my phone" are understood without the person naming a command. It changes the person's tools, so ask before installing it. It takes effect in their NEXT conversation, not this one. Say that plainly. Nothing you do later in this session will use it. 2. Install the CLI: npm i -g @vincentt-xr/cli@latest Install it globally, once. `npx @vincentt-xr/cli ` runs the same CLI without installing anything, but it re-fetches from the registry on every call, so it is slower. The global install is what this sheet uses wherever it can be reached. Check that it can be: run `vincentt version` after the install. An answer naming a version means the bare command works and the rest of this sheet is run exactly as written. If the install succeeds and `vincentt` is still not found, it is installed but not on this shell's PATH — a desktop app often does not inherit the PATH a terminal has. That is a fact about this machine, not about that one command, and it does not change during the session. From that point on, EVERY `vincentt ` on this sheet — step 3 and the whole reference below included — is run as `npx @vincentt-xr/cli ` instead. Do not install globally again; the install already worked, and repeating it fixes nothing. Do not go back to the bare command after an npx call succeeds: it will fail again for the same reason. Tell the person their global install needs PATH set up before the bare `vincentt` command will work, and that npx is what this session uses until they do. 3. Sign in: vincentt login This command PRINTS A URL and then BLOCKS, waiting for approval. As soon as you see the line "If it doesn't open, visit: ", stop and give that exact URL to the person — do not wait for the command to finish first. Print it as a bare URL on its own line, with nothing wrapped around it: no code fence, no backticks, no quotes, no trailing punctuation. Terminals only turn a URL into a clickable link when it stands alone, and this one is too long to retype. Ask them to open it and approve. The command stays running; when they approve it prints "Signed in as " and exits 0. That exit is your signal it worked — no need to ask. (If already signed in, it says so and exits immediately.) 4. Confirm setup is done, then STOP and offer the options below. Tell them, in your own words: the plugin is installed and takes effect next conversation, the CLI is installed, and they are signed in as . Then offer these, and wait for them to pick. Do not start any of them on your own. - Start a new AR app. Needs a project name (lowercase, hyphenated), which is the person's to give — ask, don't pick. Where the folder goes is not a second question: use a folder they named if they named one, otherwise make one of their own called after the project, and tell them where it went. Never the folder this tool happens to be running in. - Open a project they already have. They point you at the folder. - Nothing right now. Setup persists; a fresh conversation picks it up with the plugin loaded, which is the better place to start building. If they choose to build now, the commands are in the reference below. Prefer a fresh conversation if they are willing — that one has the plugin. REFERENCE — the commands, for when they are building: (Written as `vincentt `. On a machine where step 2 found the bare command unreachable, every one of them is `npx @vincentt-xr/cli ` instead. The project's own `preview` script handles that itself — it falls back to npx and says so — so a preview that reports the command was not found needs no global install and no intervention.) - vincentt init Scaffold a project into a new folder of that name. It installs dependencies itself and usually succeeds. Run `pnpm install` only if init reports dependencies are not installed, or a later command fails on a missing module. Use the package manager init named in its own output — the scaffold ships a pnpm lockfile, and npm in that folder produces a second lockfile and an unproven layout. - vincentt create Run from INSIDE the project folder, right after init. Reserves the project's live address so preview and publish work off the bat. (create registers a project, it does not scaffold one — that is why it runs after init, from within the folder.) - AGENTS.md Sits in the project folder and is the source of truth for building there — the dev loop, the SDK reference (GROUNDING.md), and what to edit. Read it and follow it. That means: confirm the starter runs, ask the person what they want to build (don't pick for them), then build it against GROUNDING.md. - vincentt preview Serve the app at a secure URL a phone can open (AR needs a secure context for the camera). Print the URL for the person. - vincentt publish Upload the locally built app to the reserved address.