---
title: Browser-guided setup
description: Choose SDK installation options and finish setup in your browser.
package: "@userreason/wizard"
version: "0.3.4"
since: "0.3.0"
url: https://docs.userreason.com/get-started/browser-setup/
updated: 2026-11-09
---

# Browser-guided setup

Browser-guided setup connects a terminal running in your application to the UserReason dashboard. Choose your workspace, site and installation options, then press **Continue** to start installation.

Browser-guided setup is the default in wizard 0.3.3 for production and development. The terminal flow remains available with `--terminal-setup`. Survey suggestions and the Agent test are temporarily paused; neither is shown or required to complete setup. Create surveys afterward in the dashboard.

## Start from your application

From the application directory, start the published wizard:

```sh
npx -y @userreason/wizard@latest
```

To use the terminal wizard instead, select it explicitly:

```sh
npx -y @userreason/wizard@latest --terminal-setup
```

The terminal opens a setup link. Sign in to UserReason, check the project shown, and explicitly connect the intended workspace and site. The browser link is tied to that terminal session; it is not an ongoing CLI credential. Do not share the link.

If the server has not enabled browser setup, a new connection reports that fact and continues with the ordinary terminal wizard before creating a browser setup session or applying its changes. A malformed response or a setup that already started does not silently switch installation methods.

## Choose installation options

Choose whether to install or initialize the SDK, add the UserReason agent skill, and show the optional “Powered by UserReason” attribution. The footer choice starts at **No**.

The attribution, when supported and approved, inserts a link in your application's actual page footer. It is a source change, not a badge drawn over your application by the SDK. If the wizard cannot identify a safe edit, it reports a manual step instead of guessing. Press **Continue** after choosing your installation options. The terminal applies those choices without a separate local-change approval screen. Review the resulting diff before committing it.

The browser tracks the terminal's results. A step may succeed, already be present, need manual work, or fail. Skipping SDK installation does not prove an existing integration is absent or working; verify it before publishing. Installing the agent skill does not grant access to your account or real responses.

## Finish setup

The final page shows the installation result and any remaining manual work. Package-manager failures show their actual diagnostic details in the terminal; reconnect from the same project to inspect or reconcile an incomplete attempt.

A completed setup does not publish surveys or grant ongoing CLI access. Open the dashboard and follow [Your first survey](https://docs.userreason.com/get-started/first-prompt/index.md) when you are ready to create one. Check the SDK integration and any manual installation steps before publishing.

## Resume, retry or cancel

If the terminal stops, run the resume command it printed from the same application directory. Resume uses `--resume-setup` with the existing setup ID. A setup expires after at most two hours; an expired setup needs a new run and review.

The browser keeps setup progress on the server, but the terminal must reconnect to apply or verify local work. Do not close or reload while the browser is resolving an uncertain action. Follow its retry or reconnect guidance instead of repeating the action in another session.

Cancel stops remaining setup work. It does not undo source edits already applied or remove drafts already saved. Review those results before deciding what to keep.