FAQ

Is Hexi a full autonomous agent platform?

No. Hexi is intentionally single-step and operator-driven.

Can I use Hexi without OpenRouter?

Yes. OpenAI-compatible and Anthropic-compatible adapters are included.

Where should API keys live?

Environment variables are preferred. .hexi/local.toml is an optional local fallback.

Is run history persisted?

Yes, in .hexi/runlog.jsonl.

Does Hexi edit files outside the workspace?

No. Path traversal and out-of-root writes are blocked.

How do I debug ActionPlans safely?

Use hexi plan-check to validate and hexi apply to replay deterministically.

Does Hexi need a git repo for every command?

No. hexi init, hexi onboard, and hexi doctor work in bootstrap mode without git. hexi run and hexi diff require repository context.

Can I use Hexi in CI pipelines?

Yes. Most teams use hexi doctor, hexi plan-check, and deterministic hexi apply flows in CI, and keep model-driven hexi run for local/operator-guided workflows.

How do I switch providers quickly?

Run hexi onboard again or update .hexi/local.toml manually. Then run hexi doctor to confirm provider, model, and key source.

What is the difference between hexi new and hexi demo?

hexi new is deterministic scaffolding from a chosen template. hexi demo is interactive and idea-driven, then scaffolds and can run a first customization step.

Is OpenRouter required?

No. OpenRouter support is optional. You can use openai_compat or anthropic_compat directly if those providers are configured.