Use Codex with HIPS

hi codex starts Codex on HIPS models, signed in as you, with no API key to copy: hi sets HIPS up for that session only and leaves Codex's own settings as they are.

00000000000000000000000000000000000000001curl -fsSL https://hips.com/hi.sh | sh

• hi finds codex on your computer, checks that its release is one HIPS has tested on your system, and names its vendor's installer when it is missing.
• The first time, it signs you in: it shows a code and a link, and you approve it in the Console.
• It takes a model fit for coding from your workspace's catalog, or the one you name with --model, and gives Codex HIPS's address and your sign-in through Codex's own credential setting, speaking the Responses API.
• It turns off Codex's own telemetry, and whatever would send your session to its vendor, for that session.

Code with HIPS is the overview; Coding agents has every option of hi codex.

From the signed list of tested versions of 2026-11-13, 01:44 UTC (sequence 5), joined with the releases built into hi 0.1.0. hi reads the signed list each day, so it may start a newer tested release than this page shows; any other release is refused with the tested ones named.

In the per-model agent tests' record of 2026-11-13, 01:14 UTC (sequence 5): No model has passed yet: the gateway refused each pair, because Codex always sends parallel_tool_calls: true and the gateway then read that as a requirement. Its next release reads it as a permission, as OpenAI means it, so Codex's tool calls work on HIPS once that release is live, and the pairs run again. The Console's Models page shows each model's result as the record holds it.

For people who do not use hi. Started on HIPS by hi codex; its manual setup is unvalidated.

Not tested. When the row is validated, this section states where the tool reads its base URL, key and model (environment, file, flag or UI), and which of those the setup helper uses for a session and for a persistent configuration.

Not tested. When validated: how the tool sends the key, that HIPS accepts it as Authorization: Bearer, and that the helper never prints a secret. The key is read as HIPS_API_KEY and kept on the machine's own secret store or environment.

Not tested. When validated: the backup the helper takes before a persistent change, and the selective undo that restores the previous provider, model mapping and defaults without touching unrelated providers.

• Tool and SDK versions: none tested.
• Configuration surface: not tested.
• Authentication: not tested.
• Model mapping: not tested.
• Streaming: not tested.
• Complete tool-call round trips: not tested.