Elena Artemova · Елена Артемова · Published · Updated · Purpose of the tool · With application example.
Approval is an agreement about a specific action
A person approving an action agrees not with an intention but with a specific call: the name of the operation and its arguments. If the arguments are converted to another form, filled in with default values, or rebuilt after approval, the consent referred to a different action.
That is why checking conditional approvals against the already validated arguments is not a cosmetic fix. It restores the meaning of approval: the decision receives the same object that then goes to the tool. This is a general rule for any system where a human is in the loop.
What changed in release 0.22.3
Besides approvals, the release of September 17, 2026 lists: propagating a 'tool not found' result when a server-managed session resumes; preserving command paths in POSIX form on a Windows host; correct concurrent startup of the session store; including shell calls and file edits in tool usage records; and terminating child processes when a stream closes early.
Each item looks small, but all of them concern one thing: the runtime must describe what happened in the same way before and after an interruption.
Resumption should not be silent
After an interruption, state splits into two parts: what was decided earlier and what is available now. If a tool is no longer available on resumption, the difference has to be named. Silent continuation produces a report in which an action was performed although it was not.
This is a common cause of errors in long-running processes. Observability here means not the volume of logs but the correspondence between the description and the fact. The item about child processes belongs to the same family: a finished session should not leave running processes behind.
Small things that turn into failures
Accounting for shell calls and file edits matters for limits: if these actions do not appear in the report, the spending limit is computed from incomplete data. Differences in paths between systems affect isolation: the same entry may lead to different directories.
The practical conclusion is simple: you cannot set limits and verify isolation in an environment where accounting and process lifetimes are approximate. First the description has to become accurate, and only then can it be relied upon.
Illustrative Example
Approving an action with modified arguments
- Task
- In an illustrative process the agent proposes to change a record. The person approves the call, but the application then fills the arguments with default values.
- The role of the tool
- The approval is checked against the same set of arguments that goes to the tool. If the set changes after the check, approval is requested again.
- Expected result
- The expected result is that the person's consent refers to the action actually performed, and the mismatch in arguments does not go unnoticed.
- What to check
- If approval is checked before the arguments are normalized, the check formally exists but there is no decision in substance. The example is illustrative.
An approval makes sense only when it refers to the arguments with which the action will be performed.
Source and reasons
Release date:
The primary source describes the instrument and its development. Conclusions about the choice - editorial analysis of the laboratory. An example explains the purpose of the tool; no measurements were carried out on it. Source date verified September 8, 2026.
Questions on the topic
What is dangerous about approving before the arguments are checked?
The person agrees to one call while another is executed. Formally there is approval; in substance there is none.
Why does an explicit refusal matter on resumption?
Otherwise the report describes the action as performed although the tool was unavailable.
Why account for shell calls in the report?
Otherwise the spending limit and the assessment of the work rest on incomplete data.