# fix\(server\): stop boundary claims on hook abort and read only queued runs · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/d4ac7c1029d83062f2b24f33ddc7d0e02158ad14)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: d4ac7c1029d83062f2b24f33ddc7d0e02158ad14

Requested commit: d4ac7c1029d83062f2b24f33ddc7d0e02158ad14

Commit: d4ac7c1029d83062f2b24f33ddc7d0e02158ad14

Tree: 301f311ce13a6bf3fb54701003d81ef26aa6f259

Author: Alb11747

Committer: Alb11747

## Message

```
fix(server): stop boundary claims on hook abort and read only queued runs

An aborted PostToolBatch or Stop hook interrupts its claim; the claim no
longer recovers that interruption and goes on promoting updates whose hook
response Claude has discarded. Only promotion refusals are ignored.

The claim runs at every tool batch, so it now reads only queued runs and
their messages (a new runStatuses record filter) instead of every user
message and run in the thread.

The t3_thread_send description says a queued Claude update may join the
running turn after its current tool call, and that t3_thread_wait follows it.

Co-Authored-By: Claude Opus 5.5 at high effort <noreply@anthropic.com>
Co-Authored-By: GPT-6.1 Sol at xhigh effort, review subagent <noreply@openai.com>

```

## Parents

- [ed47e6f58f2ba0109a08859c8972183a5eec83b1](https://git.cafe/pingdotgg/t3code/commit/ed47e6f58f2ba0109a08859c8972183a5eec83b1?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/d4ac7c1029d83062f2b24f33ddc7d0e02158ad14?format=markdown)