---
sidebar_position: 5
title: 5. Trigger & tail logs
pagination_prev: get-started/deploy
---

# Run a deployed agent and watch logs

## Trigger

```bash
zibby agent trigger 2b1ea07f-3ede-4bfd-a51d-431f0bab008e
```

The CLI returns immediately with a job ID:

```
✔ Workflow triggered successfully

  Job Details:
    Job ID:    ee333411-22e6-4733-b790-d480af3f662e
    Status:    running
    Version:   3
    Triggered: 02/05/2026, 10:23:13

  Monitor execution:
    zibby agent logs 2b1ea07f-... 
    zibby agent logs 2b1ea07f-... -t
```

Pass input the same way as locally:

```bash
zibby agent trigger <uuid> -p ticket=BUG-123
zibby agent trigger <uuid> --input '{"ticket":"BUG-123"}'
zibby agent trigger <uuid> --input-file ./input.json
```

If you omit the UUID, the CLI shows an interactive picker over your deployed agents.

## Tail logs (Heroku-style)

```bash
zibby agent logs 2b1ea07f-3ede-4bfd-a51d-431f0bab008e -t
```

`-t` follows live. Without `-t` it dumps the last execution and exits.

```
  Streaming logs for workflow 2b1ea07f-3ede-4bfd-a51d-431f0bab008e...
  Press Ctrl+C to stop.

2026-05-02 23:30:51.345  zibby v0.4.x
────────────────────────────────────────────────────────────
 Workflow:  my-agent
 Job:       ee333411-...
 Project:   6b60049d-...
 Agent:     cursor (model: auto)
────────────────────────────────────────────────────────────
[setup] Bundle extracted (3.2s)
[setup] Loaded MyPipelineWorkflow
[setup] Registered 5 agent strategies (...)

┌ example
│ ◆ Model: auto | key: ***bc97
│ ...
└ done 19.4s
[done] my-agent completed in 19.4s
```

The stream covers the full execution end-to-end — agent reasoning, tool calls, schema validation, completion summary.

## Multiple executions

Agent UUIDs follow the agent, not a single run. After one execution finishes, `logs -t` waits for the next trigger of the same agent and auto-switches to streaming it. Like `heroku logs --tail`.

To exit after the current run, just Ctrl+C — there's no "exit on completion" mode (yet).

## Triggering from anywhere

The CLI is the easiest way, but agents expose an HTTP API for programmatic triggering — see [Cloud → Triggering programmatically](../cloud/triggering).

## You're done

You've now scaffolded, run locally, deployed, triggered, and tailed an agent. The rest of the docs go deeper:

- [Concepts](../concepts/graph) — how the graph engine works
- [CLI Reference](../cli-reference) — every command
- [Cloud](../cloud/triggering) — HTTP triggers, log archives, bundle internals
- [Packages](../packages/agent-workflow) — package-level docs
