
PandaCode Bench Challenges T3 Code
PandaCode open-sources a reproducible streaming-chat benchmark comparing its UI with T3 Code, reporting 2,947 ms versus 8,332 ms median main-thread task time and substantially lower JavaScript heap usage. The test covers a 50,000-byte Markdown stream in headless Chrome, with documented limitations and a removed tool-output workload.
PandaCode’s results are compelling, but they demonstrate an advantage in one sustained Markdown-streaming workload—not a universal performance victory.
- –PandaCode used roughly 65% less main-thread task time and 79% less post-GC JavaScript heap than T3 Code.
- –Both apps rendered identical Markdown structures, strengthening the UI-performance comparison.
- –T3 Code still reached final paint faster, at 27 ms versus PandaCode’s 49 ms.
- –Transport decoding, desktop-shell overhead, completion handling, and tool-output rendering were excluded, so real-world results may differ.
- –PandaCode’s native Rust/Tauri architecture and incremental event coalescing appear well matched to long-running coding-agent streams.
DISCOVERED
1h ago
2026-10-30
PUBLISHED
2h ago
2026-10-30
RELEVANCE
AUTHOR
aicodeking