Motivation:

goose when it starts (brand new) shows a helpful wall of providers and config, but we can do better with an out of the box flow for those who really are new.

Solutions:

• A one click openrouter signup with model selection applied (lead, worker and editor models which are suitably low costed)
• Another choice of an ollama install + autoconfigure (checking there is capacity for this).

Between these people can hit the ground running from a cold start.

Implementation high level:

Openrouter:

• PKCE openrouter signup with oauth2.0 (which openrouter offers)
• goose crate to have core logic which is consumed by both -cli and -server
• post PKCE flow an option to top up with credits into an account

Ollama:

• ask and detect capability of running ollama locally with suitable (curated) model
• install and pull model
• auto configure goose

These can be the default choices on empty state start, or a distribution etc... (still TBD).