> ## Documentation Index
> Fetch the complete documentation index at: https://docs.generalrobotics.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Common FAQs

## Install & login

**The installer finished but `grid` is not found**

* Open a new terminal (the installer appends to your shell profile), or run
  `export PATH="$HOME/.grid/bin:$PATH"` in the current one.

**`login` opens the browser but the CLI never completes**

* The login flow runs a one-shot local callback server — make sure the
  browser and the CLI are on the same machine (over SSH, forward the port the
  CLI prints, or use a machine with a local browser). `switch` lets you pick
  a different cluster if your organization has more than one.

**Where does my cluster URL come from?**

* Your organization's GRID admin portal shows the install one-liner
  pre-filled with `--cluster-url` on its Welcome screen. If you installed
  without it, re-run the installer with that flag from the portal.

## Robots & sessions

**`robot list` shows nothing / my robot is offline**

* The robot's GRID edge runtime must be running and able to reach the
  network. Re-run `robot add` to re-verify the setup — it detects an existing
  installation and offers to reuse, repair, or overwrite it.

**Deploy fails with "No GRID API key found"**

* The runtime key is generated in the admin portal and saved for the cluster
  you paste it into. GRID asks for one at startup when the cluster it's
  pointed at hasn't got one; `robot add` asks too. Paste it there and deploy
  again. The footer names the cluster whose key is in use.

**Can I run more than one session?**

* Yes — sessions are independent. `session list` shows what's running;
  `session stop` ends a session you're done with.

## When something breaks

**Get help fast**

* `diagnostics` — bundles redacted logs + config into
  `~/grid-diagnostics-*.tar.gz`; attach it to your support ticket.
* `error` — recalls the last failure in full, including the correlation ID
  support will ask for.
* `debug on` — verbose logging for the current session; the full log lives
  at `~/.grid/logs/cli.log`.

## Isaac Sim

**How do I make the camera follow my robot?**

Add this to your session configuration:

```yaml theme={null}
viewer:
  eye: [-3.0, 0.0, 1.5] # camera location (x, y, z)
  lookat: [0.0, 0.0, 0.0]
  origin_type: asset_root
  env_index: 0
  asset_name: robot # asset name to follow
```


## Related topics

- [Your first session](/get-started/first-session.md)
- [Camera Calibration](/deployment/camera-calibration.md)