Problem

Non-main agents crash when running /compact or hitting other session file resolution paths:

Error: Session file path must be within sessions directory

Root Cause

resolveSessionFilePath() takes an optional opts.agentId to determine which agent's sessions directory to validate against. Multiple callers omit this parameter, so it defaults to the main agent's sessions dir.

When a non-main agent has an absolute sessionFile path in its session store (e.g. ~/.openclaw/agents/other-agent/sessions/xxx.jsonl), the path validation in resolvePathWithinSessionsDir() computes a relative path from the main agent's dir — which starts with ../.. — and rejects it as directory traversal.

Introduced by

Commit 4199f9889 (fix: harden session transcript path resolution) added resolvePathWithinSessionsDir as a security hardening measure for path traversal prevention. It updated resolveSessionFilePath to validate the sessionFile candidate against the sessions directory, but only updated some callers (gateway, subagent-announce, transcript) to pass agentId — missing the auto-reply paths (commands-compact, get-reply-run, status, session-cost-usage, etc.).

Before that commit, resolveSessionFilePath returned entry.sessionFile as-is with no validation, so the missing agentId was harmless.

Fix

Pass agentId to all call sites of resolveSessionFilePath() that were missing it:

• commands-compact.ts — the immediate crash site (/compact command)
• get-reply-run.ts — main reply path
• session.ts — session fork/init
• status.ts — /status transcript usage reading
• commands-status.ts — status command
• commands-session.ts — /usage command
• session-status-tool.ts — agent session status tool
• session-cost-usage.ts — cost summary, time series, and log loading (3 call sites)
• usage.ts (gateway) — usage API handlers (3 call sites)

All patched callers already had agentId available in their scope/params.

Testing

• Verified pnpm build succeeds
• The fix is a strict superset: main-agent behavior is unchanged (agentId defaults to main), non-main agents now resolve paths against their own sessions directory

Greptile Overview

Greptile Summary

This PR fixes multi-agent session transcript path validation by consistently passing agentId to resolveSessionFilePath() at call sites that resolve/validate a session’s transcript path.

The underlying issue is that resolveSessionFilePath() validates entry.sessionFile against an agent-scoped sessions directory; if callers omit opts.agentId, it defaults to the main agent’s sessions dir and rejects non-main agents’ absolute stored paths as traversal. The updates in:

• auto-reply command handlers (/compact, /status, /usage)
• the main reply run path
• session forking/init
• the session status tool
• gateway usage handlers
• session cost/usage loading helpers

ensure that non-main agents validate and resolve against their own sessions directory while leaving main-agent behavior unchanged (default remains main).

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• Changes are narrowly scoped to threading an existing agentId through to resolveSessionFilePath() and related usage loaders. Verified that resolveSessionFilePath uses agentId to select the correct agent sessions directory for validation, and that gateway session keys are canonicalized with agent:<agentId>: so the new agentId derivation is stable.
• No files require special attention

_{Last reviewed commit: ee26f95}

Context used:

• Context from dashboard - CLAUDE.md (source)
• Context from dashboard - AGENTS.md (source)