Bug type
Behavior bug (incorrect output/state without crash)
Summary
The openclaw logs --follow command reads logs from the CLI process instead of the Gateway process, causing users to miss real-time message processing logs.
Steps to reproduce
1.Start Gateway via systemd service on March 10 (e.g., openclaw gateway --port 18789)
2.On March 11, run openclaw logs --follow
3.Observe that the log file shows old date content instead of real-time Gateway logs
Expected behavior
openclaw logs --follow should automatically read the actual Gateway log file and show real-time logs of message processing.
Actual behavior
Gateway process logs to: /tmp/openclaw/openclaw-2026-03-10.log (based on startup date: March 10)
openclaw logs --follow reads: /tmp/openclaw/openclaw-2026-03-11.log (based on current date: March 11)
Users cannot see Feishu message processing logs in real-time
OpenClaw version
2026.3.2 (85377a2)
Operating system
Linux (CentOS/Rocky)
Install method
curl -fsSL https://openclaw.ai/install.sh | bash
Model
minimax2.5
Provider / routing chain
feishu ->openclaw -> minimax
Config file / key location
No response
Additional provider/model setup details
Affected: Users debugging message handling issues
Severity: Annoying / blocks workflow
Frequency: Always (when Gateway runs across date boundaries)
Consequence: Cannot see real-time message processing logs, difficult to debug issues
Logs, screenshots, and evidence
[dev@openclaw-7-37 ~]$ openclaw logs --follow
?? OpenClaw 2026.3.2 (85377a2) ? I read logs so you can keep pretending you don't have to.
Log file: /tmp/openclaw/openclaw-2026-03-11.log
01:54:51 info agents/tool-images {"subsystem":"agents/tool-images"} {"label":"prompt:images","sourceMimeType":"image/jpeg","sourceWidth":2048,"sourceHeight":1117,"sourceBytes":179423,"maxBytes":5242880,"maxDimensionPx":1200,"triggerOverBytes":false,"triggerOverDimensions":true,"outputMimeType":"image/jpeg","outputBytes":86908,"outputQuality":85,"outputMaxSide":1200,"byteReductionPct":51.6} Image resized to fit limits: 2048x1117px 175.2KB -> 84.9KB (-51.6%)
01:54:51 info agents/tool-images {"subsystem":"agents/tool-images"} {"label":"prompt:images","sourceMimeType":"image/jpeg","sourceWidth":2048,"sourceHeight":1162,"sourceBytes":139980,"maxBytes":5242880,"maxDimensionPx":1200,"triggerOverBytes":false,"triggerOverDimensions":true,"outputMimeType":"image/jpeg","outputBytes":69120,"outputQuality":85,"outputMaxSide":1200,"byteReductionPct":50.6} Image resized to fit limits: 2048x1162px 136.7KB -> 67.5KB (-50.6%)
01:55:08 info agents/tool-images {"subsystem":"agents/tool-images"} {"label":"read:/home/dev/.openclaw/media/inbound/44063812-01e5-4c86-bbf4-d2d539733019.jpg","fileName":"44063812-01e5-4c86-bbf4-d2d539733019.jpg","sourceMimeType":"image/jpeg","sourceWidth":2000,"sourceHeight":1091,"sourceBytes":275646,"maxBytes":5242880,"maxDimensionPx":1200,"triggerOverBytes":false,"triggerOverDimensions":true,"outputMimeType":"image/jpeg","outputBytes":85569,"outputQuality":85,"outputMaxSide":1200,"byteReductionPct":69} Image resized to fit limits: 44063812-01e5-4c86-bbf4-d2d539733019.jpg 2000x1091px 269.2KB -> 83.6KB (-69%)
01:55:11 info agents/tool-images {"subsystem":"agents/tool-images"} {"label":"read:/home/dev/.openclaw/media/inbound/1ea9445f-3489-4936-abd9-b57f7debf18c.jpg","fileName":"1ea9445f-3489-4936-abd9-b57f7debf18c.jpg","sourceMimeType":"image/jpeg","sourceWidth":2000,"sourceHeight":1135,"sourceBytes":221973,"maxBytes":5242880,"maxDimensionPx":1200,"triggerOverBytes":false,"triggerOverDimensions":true,"outputMimeType":"image/jpeg","outputBytes":69904,"outputQuality":85,"outputMaxSide":1200,"byteReductionPct":68.5} Image resized to fit limits: 1ea9445f-3489-4936-abd9-b57f7debf18c.jpg 2000x1135px 216.8KB -> 68.3KB (-68.5%)
02:41:20 error [tools] message failed: Unknown channel: heartbeat
[dev@openclaw-7-37 ~]$ tail -f /tmp/openclaw/openclaw-2026-03-10.log
{"0":"{\"subsystem\":\"gateway/channels/feishu\"}","1":"feishu[default]: Feishu[default] message in group oc_b87c7b0e15c81fa2d73094551dc38c8f: 上面的SQL需优化一下，将Status字段只取完课状态，输出完整的sql","_meta":{"runtime":"node","runtimeVersion":"22.22.0","hostname":"unknown","name":"{\"subsystem\":\"gateway/channels/feishu\"}","parentNames":["openclaw"],"date":"2026-03-11T05:55:35.596Z","logLevelId":3,"logLevelName":"INFO","path":{"fullFilePath":"file:///home/dev/.npm-global/lib/node_modules/openclaw/dist/subsystem-BfkFJ4uQ.js:427:14","fileName":"subsystem-BfkFJ4uQ.js","fileNameWithLine":"subsystem-BfkFJ4uQ.js:427","fileColumn":"14","fileLine":"427","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-BfkFJ4uQ.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-BfkFJ4uQ.js:427","method":"logToFile"}},"time":"2026-03-11T13:55:35.597+08:00"}Impact and severity
Affected: Users debugging message handling issues
Severity: Annoying / blocks workflow
Frequency: Always (when Gateway runs across date boundaries)
Consequence: Cannot see real-time message processing logs, difficult to debug issues
Additional information
Workaround: Use tail -f /tmp/openclaw/openclaw-2026-03-10.log to manually view the correct log file based on Gateway startup date.
Bug type
Behavior bug (incorrect output/state without crash)
Summary
The openclaw logs --follow command reads logs from the CLI process instead of the Gateway process, causing users to miss real-time message processing logs.
Steps to reproduce
1.Start Gateway via systemd service on March 10 (e.g., openclaw gateway --port 18789)
2.On March 11, run openclaw logs --follow
3.Observe that the log file shows old date content instead of real-time Gateway logs
Expected behavior
openclaw logs --follow should automatically read the actual Gateway log file and show real-time logs of message processing.
Actual behavior
Gateway process logs to: /tmp/openclaw/openclaw-2026-03-10.log (based on startup date: March 10)
openclaw logs --follow reads: /tmp/openclaw/openclaw-2026-03-11.log (based on current date: March 11)
Users cannot see Feishu message processing logs in real-time
OpenClaw version
2026.3.2 (85377a2)
Operating system
Linux (CentOS/Rocky)
Install method
curl -fsSL https://openclaw.ai/install.sh | bash
Model
minimax2.5
Provider / routing chain
feishu ->openclaw -> minimax
Config file / key location
No response
Additional provider/model setup details
Affected: Users debugging message handling issues
Severity: Annoying / blocks workflow
Frequency: Always (when Gateway runs across date boundaries)
Consequence: Cannot see real-time message processing logs, difficult to debug issues
Logs, screenshots, and evidence
Impact and severity
Affected: Users debugging message handling issues
Severity: Annoying / blocks workflow
Frequency: Always (when Gateway runs across date boundaries)
Consequence: Cannot see real-time message processing logs, difficult to debug issues
Additional information
Workaround: Use tail -f /tmp/openclaw/openclaw-2026-03-10.log to manually view the correct log file based on Gateway startup date.