hoziron trigger

Manage event triggers — create automated agent responses to events.

Synopsis

hoziron trigger <subcommand> [options]

Subcommands

hoziron trigger list

hoziron trigger list [--agent-id <id>]

Examples

# List all triggers
$ hoziron trigger list
ID                                    AGENT              PATTERN             FIRES
t-001                                 claims-agent       lifecycle           12/unlimited
t-002                                 monitor-agent      agent_spawned:*     3/10

# Filter by agent
$ hoziron trigger list --agent-id 550e8400-e29b-41d4-a716-446655440000
ID                                    PATTERN             FIRES
t-001                                 lifecycle           12/unlimited

hoziron trigger create

hoziron trigger create <agent-id> <pattern-json> [--prompt <template>] [--max-fires <n>]

Flags

Trigger Patterns

{"lifecycle": {}}
{"agent_spawned": {"name_pattern": "*"}}
{"agent_spawned": {"name_pattern": "claims-*"}}

Examples

# Lifecycle trigger (fires on agent lifecycle events)
$ hoziron trigger create 550e8400 '{"lifecycle": {}}' \
    --prompt "Agent lifecycle event: {{event}}"
✓ Trigger created (id: t-003)

# React when new agents are spawned
$ hoziron trigger create 550e8400 '{"agent_spawned": {"name_pattern": "*"}}' \
    --prompt "A new agent was spawned: {{event}}. Welcome them and offer assistance." \
    --max-fires 10
✓ Trigger created (id: t-004)

# React only to claims agents
$ hoziron trigger create 550e8400 '{"agent_spawned": {"name_pattern": "claims-*"}}' \
    --prompt "New claims agent detected: {{event}}. Verify their competency is configured."
✓ Trigger created (id: t-005)

hoziron trigger delete

$ hoziron trigger delete t-003
✓ Trigger deleted

How Triggers Work

1. An event occurs in the platform (agent created, lifecycle change, etc.)
2. The trigger pattern is matched against the event
3. If matched, the prompt template is rendered with {{event}} replaced
4. The rendered prompt is sent to the owning agent as a message
5. The agent processes it like any other message

Triggers respect max_fires — once the limit is reached, the trigger stops firing but remains configured (can be deleted or recreated with a higher limit).

See Also

• agent.md — Agents that own triggers
• cron.md — Time-based scheduling (alternative to event triggers)
• webhooks.md — External event sources