Sign up
View stargazersSign up

[Bug]: t3_thread_list and t3_thread_read default payloads are too large for polling agents#29216

opened9d agobyKkaylerberserk

Area

MCP orchestration tools: t3_thread_list, t3_thread_read

Problem

The default payloads of the thread read tools are too large for an agent that polls children. Each call fills the caller's context.

Observed

  • t3_thread_list calls with limit 25–30 returned 25–45k characters.
  • t3_thread_read returned 900–15,000 characters per item while following a child thread.
  • Managers repeat these reads while they wait, so the cost adds up over a session.
  • Version: T3 0.1.3 nightly builds, Oct–Nov 2026.

Expected

Small defaults, about 10 items, with a per-item text cap of about 500 characters. Callers ask for more with the explicit limit and maxCharsPerItem parameters.

Suggested fix

Lower the default limit and maxCharsPerItem for both tools. Return a nextPosition or equivalent cursor so callers page on demand instead of receiving everything at once.

Related, not duplicates: #27072 (recovery hint reads from position 0), #25642 (repeated linked PRs in t3_thread_read).