commit f8228d5bff7f3270c6540e02b8bf8a03abe2fe6b
parent d33129511211f5139edbb952a5aba55073b4e398
Author: andrewlaack-collab <andrew.laack@imbue.com>
Date: Wed, 4 Feb 2026 22:27:33 +0000
Updated messaging to be correct right now (#14)
Diffstat:
| M | README.md | | | 37 | ------------------------------------- |
1 file changed, 0 insertions(+), 37 deletions(-)
diff --git a/README.md b/README.md
@@ -47,20 +47,6 @@ Output formats:
- `text`
- `json`
-## CI usage
-
-Recommended CI usage is to run Vet with JSON output and display a warning if any issues are found.
-
-Example:
-
-```bash
-vet --base-commit main --output-format json > vet-report.json
-```
-
-- If Vet exits `0`, no issues were found.
-- If Vet exits `1`, issues were found (treat as a failing check).
-- If Vet exits `2`, the invocation/config is invalid (treat as a failing check).
-
## Configuration
### Model configuration
@@ -114,29 +100,6 @@ Vet supports named profiles so teams can standardize CI usage without long CLI i
Profiles set defaults like model choice, enabled issue codes, output format, and thresholds.
-## Advanced usage
-
-### Conversation history
-
-Vet can **optionally** ingest agent conversation history via a **history loader command**.
-
-#### History loader contract
-
-`--history-loader` runs a shell command and reads **stdout** as plaintext.
-
-Security note: this executes a command on your machine. Only run history loader commands you trust.
-
-- Output format: **any text**
-- Vet treats this as an opaque transcript (it may include user/assistant messages, tool calls, tool results, logs, etc.)
-- If you want Vet to catch “claimed to run tests” style issues reliably, ensure your transcript includes tool invocations/results (or other evidence), not just prose.
-
-Example:
-
-```bash
-vet "Fix flaky tests without behavior changes" \
- --history-loader "<command that prints a transcript>"
-```
-
## Privacy / telemetry
Vet does **not** collect telemetry and does not send usage data to external services.
