Prepare your host
Hagency’s documented local installation paths cover Linux and macOS. The main runtime uses Node.js 22 or later, tmux, git, and a configured coding CLI. Model access is supplied through that runtime’s supported authentication; a resource label by itself does not establish working model access.
Review before installing
Clone the repository and use the platform-specific dry run. The macOS installer uses launchd; the Linux full installer uses systemd. Review the prerequisites, generated services, and existing tmux sessions before proceeding with the documented installation.
git clone https://github.com/hagency-org/hagency.git
cd hagency
# macOS: review the installation
./install/install-macos.sh --dry-run
# Linux: review the installation
./install-full.sh --dry-runConfigure a resource, then verify it
In the September 8 development console, begin with resources: choose supported framework/model settings and define the named agents that can serve qualified roles. Publishing exposes only the intended public catalog. Provisioning or reusing an agent happens when a project request is approved.
Check observed launch and connection health. A configured resource, published role, approved request, and usable agent are distinct states. Follow the project’s error details rather than treating configuration as proof of successful execution.