Description

Session metadata transcriptPath field consistently points to the wrong directory. It uses the agents.defaults.workspace path instead of the actual agent sessions directory where transcript .jsonl files are stored.

Expected Behavior

transcriptPath should point to the actual file location, e.g.:

• Main agent: ~/.openclaw/agents/main/sessions/<sessionId>.jsonl
• Codex subagent: ~/.openclaw/agents/codex/sessions/<sessionId>.jsonl

Actual Behavior

transcriptPath points to the workspace directory for ALL sessions:

• ~/.openclaw/workspace/<sessionId>.jsonl (file does NOT exist here)

Evidence

# Session metadata says:
transcriptPath: C:\Users\..\.openclaw\workspace\79f8a379...jsonl

# File does NOT exist there:
Test-Path "...\.openclaw\workspace\79f8a379...jsonl"  # False

# File actually exists here:
Test-Path "...\.openclaw\agents\main\sessions\79f8a379...jsonl"  # True

Same pattern for codex subagent sessions — metadata says workspace, files are in agents/codex/sessions/.

Impact

• Dashboard lag/unresponsiveness: Dashboard repeatedly tries to read transcripts from non-existent paths, causing ENOENT errors
• Affects ALL session types: main, subagent, cron, discord, voice

Environment

• OpenClaw: 2026.2.17 (also present in 2026.2.14)
• OS: Windows 11 (x64)
• Node: v24.13.1
• Install method: npm global (npm install -g openclaw)

Reproduction

1. Start gateway with any agent config
2. Run sessions_list or check session metadata
3. Compare transcriptPath to actual file location on disk
4. The transcript file will be in ~/.openclaw/agents/<agentId>/sessions/ not in workspace/