mirror of https://github.com/hanzoai/agents.git synced 2026-10-30 18:48:36 +00:00

Files

T

zeekayandGitHub 5b5cf9e9db feat: merge AgentField control plane + SDKs as Hanzo Agents (#1 )

Transforms hanzoai/agents from a marketplace config repo into a full
agent orchestration platform by merging the AgentField infrastructure:

- Go control plane (K8s-like agent orchestration, service mesh, DAG workflows)
- Python SDK (FastAPI-based agent framework, LiteLLM, memory, DID/VC)
- TypeScript SDK (@hanzo/agents - Vercel AI SDK, MCP, workflows)
- Go SDK (idiomatic agent builder + client)
- React 19 embedded dashboard (XyFlow DAGs, Recharts, Radix UI)
- Docker/K8s/Helm deployment configs
- Examples: hello world, deep research, RAG, simulation, benchmarks
- Functional test suite across Python/Go/TypeScript

All references rebranded: AgentField → Hanzo Agents
- Module: github.com/hanzoai/agents/control-plane
- Python: hanzo_agents
- TypeScript: @hanzo/agents
- Go: github.com/hanzoai/agents/sdk/go
- Env vars: HANZO_AGENTS_*
- Config: hanzo-agents.yaml

Previous marketplace configs moved to config/ directory.

2026-02-09 18:53:09 -08:00

4.3 KiB

Raw Permalink Blame History

Environment Variables

This repo supports running Hanzo Agents in multiple modes (local binary, Docker, Kubernetes). Most configuration is loaded via a YAML config file and can be overridden via environment variables.

Hanzo Agents uses Viper with the prefix HANZO_AGENTS and maps nested config keys using _ (for example storage.mode → HANZO_AGENTS_STORAGE_MODE).

Control Plane (Server)

Core

HANZO_AGENTS_PORT (optional): HTTP port for the control plane (default: 8080).
HANZO_AGENTS_CONFIG_FILE (optional): Path to hanzo-agents.yaml (in containers this is typically /etc/hanzo-agents/config/hanzo-agents.yaml).
HANZO_AGENTS_HOME (recommended in containers): Base directory where Hanzo Agents stores local state (SQLite DB, Bolt DB, keys, logs). In Kubernetes, mount a PVC and set HANZO_AGENTS_HOME=/data.

Storage

Hanzo Agents supports:

local (SQLite + BoltDB, stored under HANZO_AGENTS_HOME)
postgres (PostgreSQL + pgvector)

Common:

HANZO_AGENTS_STORAGE_MODE: local (default) or postgres.

Local storage (usually not needed if HANZO_AGENTS_HOME is set):

HANZO_AGENTS_STORAGE_LOCAL_DATABASE_PATH: SQLite path.
HANZO_AGENTS_STORAGE_LOCAL_KV_STORE_PATH: BoltDB path.

PostgreSQL storage:

HANZO_AGENTS_POSTGRES_URL (preferred) or HANZO_AGENTS_STORAGE_POSTGRES_URL: PostgreSQL DSN/URL (examples below).
Alternatively, individual fields:
- HANZO_AGENTS_STORAGE_POSTGRES_HOST
- HANZO_AGENTS_STORAGE_POSTGRES_PORT
- HANZO_AGENTS_STORAGE_POSTGRES_DATABASE
- HANZO_AGENTS_STORAGE_POSTGRES_USER
- HANZO_AGENTS_STORAGE_POSTGRES_PASSWORD
- HANZO_AGENTS_STORAGE_POSTGRES_SSLMODE

Example DSNs:

postgres://hanzo-agents:hanzo-agents@postgres:5432/hanzo-agents?sslmode=disable
postgresql://hanzo-agents:hanzo-agents@postgres:5432/hanzo-agents?sslmode=disable

API Authentication (optional)

If set, the control plane requires an API key for most endpoints.

HANZO_AGENTS_API_KEY or HANZO_AGENTS_API_AUTH_API_KEY: API key checked by the control plane.

UI

HANZO_AGENTS_UI_ENABLED (default: true)
HANZO_AGENTS_UI_MODE (default: embedded)

CORS (HTTP API)

These map to api.cors.* in config. When set via env, use comma-separated values.

HANZO_AGENTS_API_CORS_ALLOWED_ORIGINS (comma-separated)
HANZO_AGENTS_API_CORS_ALLOWED_METHODS (comma-separated)
HANZO_AGENTS_API_CORS_ALLOWED_HEADERS (comma-separated)
HANZO_AGENTS_API_CORS_EXPOSED_HEADERS (comma-separated)
HANZO_AGENTS_API_CORS_ALLOW_CREDENTIALS (true/false)

Agent Nodes

Agent nodes run as separate processes/pods and register with the control plane. The most important Kubernetes-specific concept is:

The control plane must be able to reach the agent at the URL the agent registers (its callback/public URL).
In Kubernetes, this should usually be a Service DNS name (for example http://my-agent.default.svc.cluster.local:8001).

The same concept applies to Docker:

If the control plane runs in a container and the agent runs on your host, set the agent’s callback/public URL to host.docker.internal (or the Docker host gateway on Linux).
If both run in the same Docker network/Compose project, set the callback/public URL to the agent service name (for example http://demo-go-agent:8001).

Go SDK agents (example: `examples/go_agent_nodes`)

HANZO_AGENTS_URL (optional): Control plane base URL (example: http://hanzo-agents:8080).
HANZO_AGENTS_TOKEN (optional): Bearer token (use this if you enable HANZO_AGENTS_API_KEY on the control plane).
AGENT_NODE_ID (optional): Node id (default varies by example).
AGENT_LISTEN_ADDR (optional): Listen address (default: :8001).
AGENT_PUBLIC_URL (recommended in Docker/Kubernetes): Public URL the control plane will call back to (example: http://my-agent:8001).

Python SDK agents

HANZO_AGENTS_URL (recommended): Control plane base URL.
AGENT_NODE_ID (optional): Node id.
AGENT_CALLBACK_URL (recommended in Docker/Kubernetes): URL the control plane will call back to (examples: http://my-agent:8001, or for host-run agents with Dockerized control plane: http://host.docker.internal:8001).

Many Python examples also require model provider credentials (for example OPENAI_API_KEY), depending on the AIConfig you choose.

4.3 KiB Raw Permalink Blame History Unescape Escape