zeekay
901a81abe9
The docs read as OpenAI's Codex CLI: a getting-started page titled for it, `codex --enable skills` and `code sandbox macos` for commands that do not exist, defaults given as gpt-5.1-codex-max/openai when they are zen5-coder/hanzo, a Homebrew page describing a formula we do not publish. Removed three tui-stream-chunking notes and the execpolicy page: they document modules and a subcommand that live only in the vendored upstream copy. There is no execpolicy subcommand and no .codexpolicy loader in code-rs; the page told users to run something the binary does not have. Rewrote tui-alternate-screen against the source. It described an auto/always/never enum and a --no-alt-screen flag; the shipped behavior is a tui.alternate_screen bool with Ctrl+T, which replays the transcript into scrollback on the way out — a better answer to Zellij than the one written down. Genuine openai-provider documentation stays.
2.9 KiB
FAQ
Which models are supported?
The default is zen5-coder. The built-in presets also cover zen5, zen5-pro,
zen5-flash, zen5-mini, and the enso family. Pick one with /model in the
TUI or --model on the command line; the default reasoning level is medium.
The gateway is the authority on the catalog — there is no allowlist in the
client — so curl https://catalog.hanzo.ai/v1/models lists everything you can
pass to --model.
Why does o3 or o4-mini not work for me?
It's possible that your API account needs to be verified in order to start streaming responses and seeing chain of thought summaries from the API. If you're still running into issues, please let us know!
How do I stop Dev from editing my files?
By default, Dev can modify files in your current working directory (Auto mode). To prevent edits, run dev in read-only mode with the CLI flag --sandbox read-only. Alternatively, you can change the approval level mid-conversation with /approvals.
Does it work on Windows?
Running Dev directly on Windows may work, but is not officially supported. We recommend using Windows Subsystem for Linux (WSL2).
Why can't Dev find my agents on Windows?
On Windows, agent discovery can be affected by PATH configuration and file extensions. If you see errors like Agent 'xyz' could not be found, try these solutions:
1. Use absolute paths (recommended):
Edit your ~/.code/config.toml to use full paths to agent executables:
[[agents]]
name = "claude"
command = "C:\\Users\\YourUser\\AppData\\Roaming\\npm\\claude.cmd"
enabled = true
[[agents]]
name = "gemini"
command = "C:\\Users\\YourUser\\AppData\\Roaming\\npm\\gemini.cmd"
enabled = true
Replace YourUser with your actual Windows username.
2. Find your npm global install location:
Run this command to find where npm installs global packages:
npm config get prefix
The executables will be in the returned directory. For example, if it returns C:\Users\YourUser\AppData\Roaming\npm, your agent commands will be at:
C:\Users\YourUser\AppData\Roaming\npm\claude.cmdC:\Users\YourUser\AppData\Roaming\npm\gemini.cmdC:\Users\YourUser\AppData\Roaming\npm\coder.cmd
3. Verify PATH includes npm directory:
In PowerShell:
$env:PATH -split ';' | Select-String "npm"
In Command Prompt:
echo %PATH% | findstr npm
If npm's directory isn't in your PATH, you can either:
- Add it to your system PATH (requires restart)
- Use absolute paths in your config (recommended)
4. Check file extensions:
On Windows, Dev looks for executables with these extensions: .exe, .cmd, .bat, .com. Ensure your agent command includes the correct extension when using absolute paths.
Related: See agents in the configuration reference.