Decir qué hacer a continuación, en orden

[borjaperfra]

Reported from a real first run on Windows: it installed, it opened, Home explained the arrow keys, and then every data tab answered unauthorized. Nothing anywhere said to log in, and the command that does it is a subcommand you have to already know exists.

Three changes, all the same shape — the thing that has to happen next, said plainly, at the moment it has to happen.

The installer

Ends with a numbered list instead of "Run nan to get started". That line was true and not enough: printed under a warning about restarting, from a shell that could not yet find nan, to someone who then had to discover signing in on their own.

Next:

  1. Restart your terminal   close it completely and open it again
  2. nan auth login          sign in - a link goes to your email
  3. nan                     open the panel

The restart step appears only when the PATH entry was actually added, and it says to close the terminal rather than open a new tab: a terminal that keeps one process alive for all its tabs hands each new one the environment it started with.

Home

Leads with the same steps until they are done, and each drops off as it is completed rather than renumbering:

  Start here

  ✓  q               quit, so you have your shell back
  ✓  nan auth login  sign in - a link goes to your email
  ✓  nan             come back, and press right for Setup
  4. e               paste your API key in Setup
  5. space, then c   pick your tools and apply

Quitting is step one because the next step is a command in the shell, and you cannot run one with the panel open. The whole block disappears once there is nothing left to do.

The data tabs

Stop printing unauthorized. That is the platform's word for what it decided, not a word about what to do about it — they name the command now. The Models tab is the exception, since an API key opens /v1/models without a session, which is the point of Setup working without one.

Version goes to 0.1.7.