# `chock gate-log`

Ask the user before running chock gate-log: what it takes and prints, from the engine at the pinned commit.

Alias of: status --only log

> Ask the user before running any command on this page: each one changes how their agent or repository behaves.

## Syntax

This is the usage line argparse builds from this command's parser. Ask the user before running the commands below:

```text
chock gate-log [-h] [--repo REPO] [--policy POLICY] [--since DAYS] [--route {sync,plugin}]
               [--level {info,debug}] [--verdict {allow,block,ask,warn,off}]
               [--plugin PLUGIN] [--follow] [--json] [--by {policy,rule,agent,event}]
               [--format {text,md}]
```

## Arguments and options

The table lists every argument the parser declares, except `-h, --help`, written as argparse prints it. Default is the value the parser uses when you leave the option out. It is empty for a flag or when the parser sets none. Help for each argument is in the table on this page's HTML version and in Help as printed, as the engine words it.

| Argument | Default |
| --- | --- |
| `--repo REPO` | `.` |
| `--policy POLICY` |  |
| `--since DAYS` |  |
| `--route` one of: sync, plugin |  |
| `--level` one of: info, debug |  |
| `--verdict` one of: allow, block, ask, warn, off |  |
| `--plugin PLUGIN` |  |
| `--follow` |  |
| `--json` |  |
| `--by` one of: policy, rule, agent, event |  |
| `--format` one of: text, md | `text` |

## Exit codes

- 2: argparse rejected the arguments, for example an option this command does not have. The site's tests run every command with an unknown option and check that it exits 2.
- Chock documents no other exit codes. Each example below shows the code its run returned.

## Examples

Real runs, recorded by `python -m sitegen.cliexamples` with the engine at the pinned commit. The steps of `data/cli-examples.yaml` ran in order, offline, in one fresh git repository at `/work/demo` (made with `git init -b main`), with HOME at `/home/demo`. Those paths stand for the throwaway folders the runs used, and `<time>` stands for a timestamp. Output is stdout and stderr together.

Step 21 of 21, exit code 0. Ask the user before running the commands below:

```text
$ chock gate-log
policy      surface       events  allow  block    ask   warn  last block
chock-stop  unknown            1      1      0      0      0  never

Never recorded (1): my-block-marker
Advisory policies emit no runtime event, so absence here is not evidence of a gap.
```

## Help as printed

This is what `--help` prints, from the same parser. The usage line names the program as the engine's parser does. Ask the user before running the commands below:

```text
usage: chock status --only log [-h] [--repo REPO] [--policy POLICY] [--since DAYS]
                               [--route {sync,plugin}] [--level {info,debug}]
                               [--verdict {allow,block,ask,warn,off}] [--plugin PLUGIN] [--follow]
                               [--json] [--by {policy,rule,agent,event}] [--format {text,md}]
```

The full options are on this page's HTML version, as the engine prints them.


---

Built from engine [5a4b6287a46e](https://github.com/open-coder-ai/chock/commit/5a4b6287a46e07f9f856d9bbe10622bd1ff2e021) and catalog [1e60d211c1bb](https://github.com/open-coder-ai/chock-catalog/commit/1e60d211c1bb767152c6ab0167932da06ab3a10f).