§ PL j ãóZ—dZddlmZddlmZmZdZdZdZdd „Z dd „Z dd„Z dd„Z dd„Z dS)uçConfigurable tool-output truncation limits. Ported from anomalyco/opencode PR #23770 (``feat(truncate): allow configuring tool output truncation limits``). OpenCode hardcoded ``MAX_LINES = 2000`` and ``MAX_BYTES = 50 * 1024`` as tool-output truncation thresholds. Hermes-agent had the same hardcoded constants in two places: * ``tools/terminal_tool.py`` — ``MAX_OUTPUT_CHARS = 50000`` (terminal stdout/stderr cap) * ``tools/file_operations.py`` — ``MAX_LINES = 2000`` / ``MAX_LINE_LENGTH = 2000`` (read_file pagination cap + per-line cap) This module centralises those values behind a single config section (``tool_output`` in ``config.yaml``) so power users can tune them without patching the source. The existing hardcoded numbers remain as defaults, so behaviour is unchanged when the config key is absent. Example ``config.yaml``:: tool_output: max_bytes: 100000 # terminal output cap (chars) max_lines: 5000 # read_file pagination + truncation cap max_line_length: 2000 # per-line length cap before '... [truncated]' The limits reader is defensive: any error (missing config file, invalid value type, etc.) falls back to the built-in defaults so tools never fail because of a malformed config. é)Ú annotations)ÚAnyÚDictiPÃiÐÚvaluerÚdefaultÚintÚreturncój— t|¦«}n#ttf$r|cYSwxYw|dkr|S|S)z@Return ``value`` as a positive int, or ``default`` on any issue.r)rÚ TypeErrorÚ ValueError)rrÚivs úShortcut for file-ops callers that only need the per-line cap.rr#r$r%rÚget_max_line_lengthr+Zs€å !Ñ #Ô #Ð$5Ô 6Ð6r%N)rrrrr r)r r)r r)Ú__doc__Ú __future__rÚtypingrrrrrrr!r&r)r+r$r%rúr/s½ðððð>#Ð"Ð"Ð"Ð"Ð"àÐÐÐÐÐÐÐð ÐØÐØÐððððððððð21ð1ð1ð1ð 1ð1ð1ð1ð 7ð7ð7ð7ð7ð7r%