Skip to content
HyperlakeHyperlake

Agents and workflows

Agents

Section titled “Agents”
Terminal window
hyperlake agent list
hyperlake agent chat --agent AGENT_ID --message 'Summarize the latest policy failures' --chat-name investigation
hyperlake agent projects --conversation CONVERSATION_ID --operation add --cluster CLUSTER_ID

An agent is a configured capability context. Project or cluster associations scope the resources available to a conversation; they do not grant permissions beyond the authenticated identity.

Goal workflows

Section titled “Goal workflows”
Terminal window
hyperlake goals templates
hyperlake goals build --prompt 'Check whether policy sync is healthy'
hyperlake goals validate --file goal.yaml
hyperlake goals create --file goal.yaml
hyperlake goals run --goal GOAL_ID
hyperlake goals status --run RUN_ID

Goal definitions should describe the desired outcome, success criteria, allowed actions, and approval requirements. A successful goal submission is not proof that the outcome was achieved; inspect the run status and evidence.

A2A

Section titled “A2A”
Terminal window
hyperlake a2a discover --url AGENT_CARD_URL
hyperlake a2a send --url AGENT_URL --message 'Inspect the approved target'

A2A connects Hyperlake to an external agent endpoint. Use --token-env for a bearer token held in an environment variable. Private or HTTP endpoints require explicit --allow-private.