Should the Read tool respect opencode config values for max_bytes and max_lines?

[wellescastro]

Question

The Read tool currently uses hardcoded constants for truncation: 50KB for bytes and 2000 for line count, instead of honoring configuration from tool_output.max_bytes or tool_output.max_lines in opencode config.

Other tools (such as Shell) do respect these config values via the Truncate service. Is this hardcoded behavior in the Read tool by design, or is it ok to adjust Read's behavior to use the Truncate service/configured limits like the other tools?

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Multiple problems with current truncation implementation #13770: Covers the same concern — MAX_LINES/MAX_BYTES being hardcoded and not configurable in the truncation implementation
• [FEATURE]: Make read tool MAX_LINE_LENGTH configurable (currently hardcoded at 2000 chars) #25337: Related feature request to make the Read tool's MAX_LINE_LENGTH configurable (also hardcoded)