Repository navigation
perf(agent-runtime): skip thinking token progress persistence - #465
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe runtime now excludes ChangesTransient storage filtering
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
core/agent-runtime/src/AgentRuntime.tsESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox. core/agent-runtime/src/MessageConverter.tsESLint skipped: the ESLint configuration for this file references a package that is not available in the sandbox. core/agent-runtime/test/AgentRuntime.test.tsESLint skipped: the ESLint configuration for this file references a package that is not available in the sandbox.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Summary
system/thinking_tokensprogress counters from thread message persistence/runs/streamand run-event replaythinkingcontentMessageConverterandAgentRuntimeintegration levelsRoot cause
After a run commits, the incremental message flusher attempts to mirror every executor message into the thread store.
thinking_tokensis emitted frequently as a progress counter, so persisting it creates one awaited remote append per update on OSS/FUSE-backed stores and backpressures consumption of subsequent model events.The counter is transient metadata rather than conversation history. Filtering it at the existing storage boundary removes that write amplification without changing the streaming protocol or final transcript.
Validation
core/agent-runtime:ut run test(210 passing)core/agent-runtime:ut run tsccore/agent-runtime:ut run tsc:pubut run lintSummary by CodeRabbit