Docs
for daily use and debugging.

Start with installation and configuration, use the shell-first verification flow for routing checks, then move to the TUI only for UI-specific validation.

Start here

The installation guide is the best entry point for most people. It covers setup, the current slash commands, execution policy, routing behavior, Azure Data Explorer queries, and the shell-first verification flow. If you are running Harper with the local HTTP interface enabled, the API Server page explains the runtime model, configuration, and integration details. When something goes wrong in local development, the troubleshooting guide is the right place to check for auth, shell, and runtime issues.

Verification workflow

Use harper-batch before opening the TUI when you need to verify routing, normalization, or follow-up behavior. This keeps the verification path close to the core chat flow and removes UI state from the first debugging step.

cargo run -p harper-ui --bin harper-batch -- --strategy deterministic --prompt "where is execution strategy used in this repo"
cargo run -p harper-ui --bin harper-batch -- --strategy deterministic --prompt "run the git status" --prompt "run that"
cargo run -p harper-ui --bin harper-batch -- --strategy grounded --prompt "where is execution strategy used in this repo"

Read ROUTING, DETERMINISTIC INTENT, NORMALIZED COMMAND, ACTIVITY, and ASSISTANT first. Those fields tell you whether Harper chose the right path before you spend time checking the TUI.

Deeper reading

If you want the longer reference material, the full user guide still lives in the repository. The main pages are About Harper, Chat Interface, Configuration, Azure Data Explorer, and Quick Start. Use this page as the short path through the product, and use the repository docs when you need the full detail.