Dependencies and blast radius

Before a destructive or live-affecting change, ask the platform who depends on what:

cai deps                  # dependencies for the pinned workflow
cai deps --account        # the whole account's dependency map

The output maps workflows to the agents that use them as tools and to the workflows that call them as subflow targets — the blast-radius answer for the three questions that matter:

1. “Can I delete this?” A workflow a live shared agent depends on is not a free delete. (cai workflow delete refuses when agents depend on it unless forced — the guard exists because this mistake is common.)
2. “What does publishing this change?” Workflow tools always follow the latest live release, so every dependent live agent changes the moment you publish. Publishing a shared dependency is a production change.
3. “Why did that agent’s behavior change?” Walk the dependency edge backwards, then check the activity feed for the publish that did it.

Example prompts

Run cai deps --account and tell me which workflows are load-bearing for shared agents — those are the ones whose publishes I want to treat like deploys.