Decir que está trabajando, y qué hacer cuando termina

[borjaperfra]

Reported: pressed c to configure Codex and the panel froze — no repaint, no key accepted, no idea whether it was working or hung.

It was working. configureTools ran straight out of the key handler, on the event loop, and with Hermes in the list that is four processes and several seconds of a panel that cannot draw.

It runs as a command now, with the spinner and a line saying what is taking the time:

  Tools
  ⣾  writing the configs - a few seconds, Hermes is asked rather than written

space is refused while that runs, because it reorders the list the run is walking.

And then the other half of the same question

The tab said 5 added and stopped. That is what it did, not what a member is left holding — which is how to actually use any of it.

  Now open them

  opencode       then /models inside it, and pick a NaN one
  codex          already aimed at the cluster; codex --model <id> to switch
  pi             NaN is already its default provider
  droid          pick a model with (NaN) in its name
  hermes doctor  says whether the provider answers, then talk to it

Each step is the one that tool's own page on nan.builders publishes under "check that it works".

configureTools returns which tools it wrote, so that list is the tools actually configured rather than a fixed block of text. A test fails if a tool the Setup tab can configure has nothing to say about using it.

Version goes to 0.1.12.