Prior attempts on an entity
prior_attemptsRetrieve prior change attempts on an entity to avoid repeating rejected edits. Shows inferred outcomes (reverted or active) and reasons.
Instructions
Prior change attempts on an entity, each with an inferred outcome.
Call this BEFORE editing an entity. If the same change was tried before
and reverted, you get the prior reasoning and change_type plus an
inferred outcome — so you can change your plan instead of repeating a
rejected approach.
Each result is a change event with three extra fields:
outcome— "reverted" (a later remove/delete on the same path) or "active" (no later removal seen).confidence— "proximity_high" or "proximity_low".outcome_reasoning— the reverting event's reasoning (WHY it was rejected), or "" while still active.
Outcome is inferred from add->remove proximity — v0.3.7 has no explicit reject/revert change types yet (those arrive in v0.3.11). Output is templated, deterministic, and makes no LLM call. This is a pull-only tool: it never writes and never pushes; you decide when to ask.
Conservative by design — min_confidence defaults to "proximity_high",
so an empty list (nothing clearly tried-and-rejected) is the normal,
preferred answer over a speculative false positive. Pass
min_confidence="proximity_low" to widen recall.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entity_path | No | The entity you're about to change. Exact path with prefix matching — 'users' also covers 'users.email'. Examples: 'src/auth.py::login', 'users.email', 'env/STRIPE_SECRET_KEY'. Provide this OR `description`. | |
| description | No | Free-text description of what you're about to do, when you don't have an exact entity_path. Matched as a substring against prior reasoning, diffs, and entity paths. Provide this OR `entity_path` (entity_path takes precedence if both are given). | |
| min_confidence | No | Confidence floor. 'proximity_high' (default) returns only attempts that were clearly tried and then reverted within the window — the high-signal 'rejected before' cases. Pass 'proximity_low' to also see the noisy tail (still-active changes and far-apart reverts). | proximity_high |
| window_minutes | No | Proximity window in minutes for the add->remove revert heuristic. An attempt removed within this many minutes is 'proximity_high'; beyond it, 'proximity_low'. Default 10080 (7 days). | |
| limit | No | Maximum number of results. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |