Files
dev/docs/faq.md
T
zeekay dae0dcad42 feat: rename code-rs to hanzo-dev and prepare for publication
🎯 Major directory restructure and publication preparation:

**Directory Rename:**
- Renamed code-rs/ → hanzo-dev/ for better branding alignment
- Updated all build scripts, GitHub workflows, and documentation
- Fixed all path references across the codebase

**Publication Setup:**
- Updated workspace version to 0.6.0 (production ready)
- Configured main CLI crate as 'hanzo-dev' (available on crates.io)
- Set publish = true for core crates (hanzo-core, hanzo-tui)
- Added proper package metadata (description, license, repository, etc.)
- Maintained internal crate names to minimize dependency changes

**Updated Components:**
- package.json build scripts now reference hanzo-dev/
- GitHub Actions workflows updated for new directory structure
- build-fast.sh and related scripts updated
- Documentation and README references updated
- All Cargo.toml manifests updated with publication metadata

**Publishing Strategy:**
- Main binary: hanzo-dev (new, available for publication)
- Core library: hanzo-core (existing name, ready to publish)
- TUI library: hanzo-tui (existing name, ready to publish)
- Avoids conflict with existing Hanzo AI infrastructure crates

This prepares the codebase for official publication to crates.io while
maintaining full compatibility with the existing build system and
providing clear branding as 'Hanzo Dev' CLI tool.
2026-01-14 16:49:45 -08:00

3.1 KiB

FAQ

Only by name. The 2021 Codex model was deprecated in March 2023. Hanzo Dev is a community fork of the openai/codex CLI and continues to evolve separately.

Which models are supported?

We recommend the built-in Hanzo Dev presets that wrap GPT-5.2 (for example dev-gpt-5.2-dev). The default reasoning level is medium, and you can upgrade to high for complex tasks with /model.

You can also use older models by using API-based auth and launching Hanzo Dev with the --model flag.

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 Hanzo Dev from editing my files?

By default, Hanzo 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 Hanzo Dev directly on Windows may work, but is not officially supported. We recommend using Windows Subsystem for Linux (WSL2).

Why can't Hanzo 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 ~/.hanzo/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.cmd
  • C:\Users\YourUser\AppData\Roaming\npm\gemini.cmd
  • C:\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, Hanzo 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 the Agent Configuration Guide for more details.