ZeroClaw preserves Gemini thought signatures across tool calls

zeroclaw-labs/zeroclaw PR #8935 is the primary source for today’s ZeroClaw item: “fix(agent): preserve Gemini thought signatures in tool-call history.” ClawCharts placed ZeroClaw on the assignment desk at rank #5, but the public claim comes from the inspected source cluster, not the medal.

The facts: current baseline resolves to zeroclaw-labs/zeroclaw; the observed row showed None seven-day stars, unknown active contributors, unknown commits, and 32232 total stars; GitHub reports 32232 stars, 523 open issues, default branch master, pushed_at 2026-07-11T23:50:27Z; release baseline is v0.8.2 (2026-06-26T04:34:52Z).

What changed: fix(agent): preserve Gemini thought signatures in tool-call history. The source is current to 2026-07-12T00:48:40Z. Related/context links inspected for the cluster: zeroclaw-labs/zeroclaw PR #9003 — docs(maintainers): fix dashboard workflow link; zeroclaw-labs/zeroclaw PR #8928 — feat(zerocode): show active resolved log path in Doctor diagnostics (#8650); zeroclaw-labs/zeroclaw issue #8766 — [Feature]: Add user-behavior E2E coverage for first-run setup; zeroclaw-labs/zeroclaw PR #8992 — feat(memory): add Hindsight as a first-class memory backend.

Why it matters: this is memory and session-state work, the sort of plumbing that determines whether agent infrastructure is observable, governable, and recoverable under operator load.

Current: repo/product baseline, releases, PRs, issues, and community/discovery search surfaces were checked. Weak community hits, duplicate package mirrors, ambiguous name collisions, and stale keyword-only matches were rejected rather than promoted.

Caveat: GitHub-source items can describe work in motion rather than shipped product behavior, so this is filed as source-inspected operator news, not a release claim.

Operator context: the primary artifact is zeroclaw-labs/zeroclaw PR #8935, titled “fix(agent): preserve Gemini thought signatures in tool-call history.” It was selected after comparing the current repo, release baseline, recently updated pull requests and issues, and the public discovery surfaces used for this edition. The claim is deliberately narrow: the source shows current project motion or, for a quiet watchlist, the absence of a stronger fresh public event. It does not turn an unmerged proposal into shipped behavior, and it does not treat the ClawCharts position as evidence for the underlying claim.

Source cluster: zeroclaw-labs/zeroclaw PR #9003: docs(maintainers): fix dashboard workflow link; zeroclaw-labs/zeroclaw PR #8928: feat(zerocode): show active resolved log path in Doctor diagnostics (#8650); zeroclaw-labs/zeroclaw issue #8766: [Feature]: Add user-behavior E2E coverage for first-run setup; zeroclaw-labs/zeroclaw PR #8992: feat(memory): add Hindsight as a first-class memory backend. These links are grouped because they show the adjacent operator surface around ZeroClaw, not because every item is equally important. The primary source carries the headline; supporting links provide comparison, implementation context, or evidence that the selected angle is not an isolated keyword hit. Package mirrors and generic search residue were excluded.

Operational reading: for teams evaluating ZeroClaw, the useful question is whether this work changes a trust boundary, control surface, integration seam, or maintenance burden. The current evidence is enough for a watch-or-test decision, not for an unconditional rollout recommendation. Operators should inspect merge or closure state, confirm the behavior against the version they run, and keep the caveat attached until the project’s own shipped baseline catches up. That boundary is dull but useful; infrastructure tends to punish decorative certainty.

Source-inspected operator brief; ClawCharts is assignment context, not claim evidence.