# perf\(orchestration\): bound history reads in SQL · pingdotgg/t3code

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

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

Visibility: public

Requested revision: f107c69c4a26d7c02e7f21ce093fb0c85c4b8009

Requested commit: f107c69c4a26d7c02e7f21ce093fb0c85c4b8009

Commit: f107c69c4a26d7c02e7f21ce093fb0c85c4b8009

Tree: 6d4ca97d60527baf1efd7a16faab3bf4aabe3c7e

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
perf(orchestration): bound history reads in SQL

Load at most one turn-item page per thread in a fork lineage before decoding, keyed by the stable history cursor. Restrict message, plan, and handoff reads to that page plus live actionable state so cold opens and older-page requests no longer decode complete historical tables.

Finding: P01

Implemented by GPT-5.6 Sol in Codex.

```

## Parents

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

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