---
title: "oz0 plugin explain"
description: "Usage and flags for oz0 plugin explain."
canonical_url: "https://docs.oz0.ai/reference/cli/oz0/plugin/explain"
---
# oz0 plugin explain

> Usage and flags for oz0 plugin explain.

For: Operators and developers looking up a command.

Writes four files into --out: diagram.svg (the plugin's graph, laid out as the studio draws it, legible printed in black and white), diagram.mmd (the same graph as a Mermaid flowchart), summary.html (one printable page: what the plugin and each flow do, the steps, approvals, the tool-policy rules that apply with their IDs, data rules, purposes and legal bases, recipients, budgets, the coverage figure when the files hold a coverage report, the version and digests) and explain.json (the same facts as data).

Print the page to PDF from a browser. The same files and settings give the same bytes, so two exports diff cleanly. The tenant's tool policy and data rules are included when you hold governance.read, its purposes, legal bases and recipients when you hold inventory.read; the page says what was left out. Each export is audited. The page describes what the files and settings state; it is not an assessment.

With a name, the installed version in the tenant; with --dir, a local plugin folder, read without a server and without the tenant's settings.

## Usage

```bash
oz0 plugin explain [<name>] --out <dir> [flags]
```

## Flags

<table>
<thead>
  <tr>
    <th>
      Flag
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Default
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        --coverage
      </code>
    </td>
    
    <td>
      string
    </td>
    
    <td>
      
    </td>
    
    <td>
      with --dir: a coverage report (plugin test --coverage-out) instead of the folder's evals/coverage.json
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        --dir
      </code>
    </td>
    
    <td>
      string
    </td>
    
    <td>
      
    </td>
    
    <td>
      a local plugin folder to explain instead of an installed plugin
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        --flow
      </code>
    </td>
    
    <td>
      string
    </td>
    
    <td>
      
    </td>
    
    <td>
      keep one flow, its steps and what they run
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        --out
      </code>
    </td>
    
    <td>
      string
    </td>
    
    <td>
      
    </td>
    
    <td>
      the folder to write diagram.svg, diagram.mmd, summary.html and explain.json into
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        --tenant
      </code>
    </td>
    
    <td>
      string
    </td>
    
    <td>
      <code>
        default
      </code>
    </td>
    
    <td>
      the tenant
    </td>
  </tr>
</tbody>
</table>

## Inherited flags

<table>
<thead>
  <tr>
    <th>
      Flag
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Default
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        --context
      </code>
    </td>
    
    <td>
      string
    </td>
    
    <td>
      <code>
        $OZ0_CONTEXT or &lt;config dir>/orchestrator-zero/context.json
      </code>
    </td>
    
    <td>
      CLI context file written by server init
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        --log-level
      </code>
    </td>
    
    <td>
      string
    </td>
    
    <td>
      <code>
        info
      </code>
    </td>
    
    <td>
      log level: debug, info, warn or error
    </td>
  </tr>
</tbody>
</table>

See [all `oz0` commands](https://docs.oz0.ai/reference/cli/oz0) and the [global flags](https://docs.oz0.ai/reference/cli/oz0#global-flags).


## Sitemap

See the full [sitemap](https://docs.oz0.ai/sitemap.md) for all pages.