Connect a provider first. Add agent only lists hosts that Settings already knows.
1

Open Add agent

In the participant list, click + Add agent.
2

Pick the connected host

The list is the Settings rail: connected API hosts plus seat-ready CLI harnesses. Empty name becomes the host’s short label (Ollama, Grok, Local, …), not “Claude”.
3

Optional: role, prompt, model

  • Role — shapes the default tool grant and boot charter.
  • System prompt — extra instructions on top of porto’s operating manual.
  • Model — leave blank for the provider default. Local / Ollama show the live list from the host.
4

Submit, then talk

The seat appears in the participant list immediately. Type in the composer and address it (@name or pick it). The first reply is the proof the stack works.

​
What you should not do

  • Do not paste an API key into Add agent. That field is gone. Keys live in Settings.
  • Do not add a second seat just to change models. Open the agent panel or Settings → Agents and change provider / model on the same handle.

​
First-token wait (local)

Ollama and Local / network seats wait up to five minutes for the first token. A cold Qwen load looks stuck; it is not. Cloud and CLI seats use the normal shorter watchdog.

​
If the seat errors on the first turn

Settings → Providers. The host you picked must show as connected. Re-save the key or URL.
Start the backend from a terminal where which grok (or claude / codex) works. See CLI harnesses.
From the API machine: curl -s "$BASE_URL/models" (or Ollama curl -s http://127.0.0.1:11434/api/tags). If that fails, porto cannot list or complete.