# fix\(server\): remote task followers read only their own task · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 70a2a7bdd25d1c3729a864517727914fc3b01d2b

Requested commit: 70a2a7bdd25d1c3729a864517727914fc3b01d2b

Commit: 70a2a7bdd25d1c3729a864517727914fc3b01d2b

Tree: f48b5c6f25bfc8e1b0cf5b70907caf415b883d8d

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(server): remote task followers read only their own task

RemoteDelegation.start resumes every open remote task at once, and each
follower read its parent's whole subagent list to find one task, then held
it across a wait of up to ten minutes. A parent with 1,441 tasks (35 MB of
payload) and 122 open ones made every restart decode ~170k records and hold
8 GB, so the server ran out of heap seconds after starting and crash-looped.

getThreadRecords now takes a subagentIds filter. Followers, and task_status
waits that re-read on every parent subagent.updated, read just their task.
Against a copy of the affected database the startup fan-out drops from 8.2 GB
retained over 21.6 s to 8 MB over 61 ms.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

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

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