antithesis ยท diff

git:20261107.35c08e5 to git:20261113.902c452

9 added, 8 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]"
+ argument-hint: "[triage|debug|workload|launch|properties] <prompt>"
---
# Antithesis
- Plugin version: `0.0.9`
+ Plugin version: `0.1.0`
## 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
+ - **snouty 0.10.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.
+ Assume that dependencies are set up. If any command fails, check dependencies and `snouty doctor` first.
+ If you are completely stuck on something outside the user's control, tell the user where to get help: <support@antithesis.com> for their tenant or runs, GitHub issues on `antithesishq/antithesis-plugin` or `antithesishq/snouty` for a bug in either, and the Antithesis Discord (<https://discord.com/invite/antithesis>) for questions.
+
## Modules
- Pick the module from the first argument, then read only that module's `MODULE.md`.
+ If the first argument names a module, 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.
+ Otherwise the request is a free-form prompt: read `references/workflows/MODULE.md`, and derive a workflow from it.
- 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 keep working toward the user's goal, within the budget, until it is met or you are blocked on something only the user can decide. A module's steps are a means to the goal, not its end. While other work remains, don't end your turn on a question: write it in a file the user will see, tell them where, and keep working.
+ 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. If the user gives no compute budget, use 60 compute hours for the whole task, across every module and run. Then keep working toward the user's goal, within the budget, until it is met or you are blocked on something only the user can decide. A module's steps are a means to the goal, not its end. While other work remains, don't end your turn on a question: write it in a file the user will see, tell them where, and keep working.