mirror of
https://github.com/hanzoai/dev.git
synced 2026-10-25 03:32:32 +00:00
zooqueen
d70acafded
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.
codex-core
This crate implements the business logic for Codex. It is designed to be used by the various Codex UIs written in Rust.
See also: Slash Commands for a complete list of interactive commands available in the TUI.
Dependencies
Note that codex-core makes some assumptions about certain helper utilities being available in the environment. Currently, this
macOS
Expects /usr/bin/sandbox-exec to be present.
Linux
Expects the binary containing codex-core to run the equivalent of codex debug landlock when arg0 is codex-linux-sandbox. See the codex-arg0 crate for details.
All Platforms
Expects the binary containing codex-core to simulate the virtual apply_patch CLI when arg1 is --codex-run-as-apply-patch. See the codex-arg0 crate for details.