zooqueen d70acafded dev answers without an account, on the free pool ...

Installing dev and running it got you a sentence telling you to go get a key.
The gateway will answer without one — the free pool costs nothing to serve — so
the first run now asks it instead of refusing.

The credential and the model move together, because either alone is broken: the
free key may only ask for a route that costs nothing, and a coding model asked
with it is refused. `free` is the pool's own id rather than a vendor `:free`
one, so the routes underneath can be retired without reaching this binary.

An account still wins wherever both exist, and a build with no free key behaves
exactly as it did before — the refusal it used to give is what remains when
there is nothing to ask with.

The TUI stopped offering to sign the user in to OpenAI on the way past. It was
reading auth.json alone, so a Hanzo bearer — the one `hanzo code` sets on the
child, and now the free one — looked like no credential at all.

2026-08-14 23:02:45 -07:00

..

src

dev answers without an account, on the free pool

2026-08-14 23:02:45 -07:00

Cargo.toml

feat(exec,app-server): a real JSON contract, and steering that does not abort

2026-08-06 01:13:15 -07:00