antithesis ยท diff
git:20261105.a3ae605 to git:20261105.c6e4dcc
1 added, 1 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: antithesis
description: Entry point to Antithesis. Use for any task that involves Antithesis.
argument-hint: "[triage [monitor|summary|root-cause]|debug|workload|launch|properties] [target]"
---
# Antithesis
- Plugin version: `0.0.9-rc.1`
+ Plugin version: `0.0.9`
## Before starting
1. If you are running on one of these platforms, read its notes:
- Devin: `references/platforms/devin.md`
- Replit: `references/platforms/replit.md`
2. Read `references/antithesis/explainer.md`.
3. Check the dependencies below.
### Dependencies
Every module needs:
- **snouty 0.9.0 or later**, installed and configured for the Antithesis tenant. If it's missing or not configured, follow `references/antithesis/snouty-setup.md`. If it's older, run `snouty update`, or reinstall it if it wasn't installed with the installer script
- **Docker or Podman, with Docker Compose**
- **jq**
Assume that dependencies are setup. If any command fails, check dependencies and `snouty doctor` first.
## Modules
Pick the module from the first argument, then read only that module's `MODULE.md`.
| Argument | Module | Use when |
| ------------ | --------------------------------- | ------------------------------------------------------------- |
| `triage` | `references/triage/MODULE.md` | Analyze a run for failures, monitor an in progress run. |
| `debug` | `references/debug/MODULE.md` | Execute commands in Antithesis to debug a moment or property. |
| `workload` | `references/workload/MODULE.md` | Building or iterating on a workload. |
| `launch` | `references/launch/MODULE.md` | Launching a new run of a workload with `snouty launch`. |
| `properties` | `references/properties/MODULE.md` | Importing the SUT's guarantees or defining a new one. |
If there is no argument, infer the module from the request. If it is still ambiguous, ask.
Once you've read the module's `MODULE.md`, if the task will run unattended for a long time, such as building a workload or launching and following runs, ask the user up front, in one message, for anything you can foresee needing: a compute budget, permission to change their code, the scope, where to report issues, and any choice the module leaves to the user. Then work to the end without stopping, unless you are blocked.