PR #65029: fix(sessions): allow env override for sessions_history text truncation limit

• Repository: openclaw/openclaw
• Author: hclsys
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/65029

Description (problem / solution / changelog)

Summary

SESSIONS_HISTORY_TEXT_MAX_CHARS was hardcoded to 4000 in src/agents/tools/sessions-history-tool.ts, unlike PI_BASH_MAX_OUTPUT_CHARS which reads from env via readEnvInt(). Users with large context windows or long conversation histories had no way to increase the per-entry text truncation limit.

Fixes #64970

Root cause

// sessions-history-tool.ts:32 (before fix)
const SESSIONS_HISTORY_TEXT_MAX_CHARS = 4000;  // hardcoded, no env override

// bash-tools.exec-runtime.ts:105 (existing pattern)
readEnvInt("PI_BASH_MAX_OUTPUT_CHARS"),  // reads from env, falls back to default

Fix

const SESSIONS_HISTORY_TEXT_MAX_CHARS = readEnvInt("SESSIONS_HISTORY_TEXT_MAX_CHARS") ?? 4000;

Matches the existing env-override pattern used by PI_BASH_MAX_OUTPUT_CHARS and OPENCLAW_BASH_PENDING_MAX_OUTPUT_CHARS in bash-tools.exec-runtime.ts. Import added from ../bash-tools.shared.js where readEnvInt is already exported.

Scope

• Files: sessions-history-tool.ts (+6/-1)
• Production LOC: 1 line changed (+ import + comment)
• oxlint clean
• Zero competing PRs

Credit to @Galaxy-Chen for identifying the inconsistency in #64970.

Changed files

• src/agents/tools/sessions-history-tool.ts (modified, +11/-1)