Common FAQs

​

Install & login

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

• 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.

• Your organization’s GRID admin portal shows the install one-liner pre-filled with --cluster-name/--cluster-url on its Welcome screen. If you installed without it, re-run the installer with those flags from the portal.

​

Robots & sessions

• 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.

• The runtime key is generated in the admin portal and stored when you run robot add. Re-run robot add (or set GRID_CORTEX_API_KEY in your shell) and deploy again.

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

​

When something breaks

• 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

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