Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feature Request: Restore formatted gateway startup log output [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73187•Fetched 2026-04-29 06:22:23
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
xupeijianxupeijian
Participants
xupeijianxupeijian

Code Example

agent model: bailian/qwen3.6-plus
ready (5 plugins: browser, feishu, lossless-claw, memory-core, qqbot; 24.0s)
log file: C:\\Users\\Administrator\\.openclaw\\openclaw.log

---

═══════════════════════════════════ 🐾 OpenClaw Gateway ═══════════════════════════════════
🔑 Auth: password (openclaw.json) + no token
🌐 Server: http://127.0.0.1:18789/
🤖 Agent: ark-code-latest (volcengine-plan)
🧩 Plugins: 5 loaded (browser, feishu, lossless-claw, memory-core, qqbot)
📝 Log file: C:\\Users\\Administrator\\.openclaw\\openclaw.log

[health-monitor] started
[heartbeat] started
RAW_BUFFERClick to expand / collapse

Feature Request

Current behavior:

The gateway startup log output has been simplified to just 3 plain lines:

agent model: bailian/qwen3.6-plus
ready (5 plugins: browser, feishu, lossless-claw, memory-core, qqbot; 24.0s)
log file: C:\\Users\\Administrator\\.openclaw\\openclaw.log

Previous behavior:

The startup log had a well-formatted, structured output with sections:

═══════════════════════════════════ 🐾 OpenClaw Gateway ═══════════════════════════════════
🔑 Auth: password (openclaw.json) + no token
🌐 Server: http://127.0.0.1:18789/
🤖 Agent: ark-code-latest (volcengine-plan)
🧩 Plugins: 5 loaded (browser, feishu, lossless-claw, memory-core, qqbot)
📝 Log file: C:\\Users\\Administrator\\.openclaw\\openclaw.log

[health-monitor] started
[heartbeat] started

Why this matters:

  1. Quick status visibility: The old format made it instantly clear what auth mode, server URL, and agent model were active. The new minimal format requires digging through config files to verify these.

  2. Health monitoring clarity: The old format explicitly logged [health-monitor] started and [heartbeat] started status lines, which were useful for operators to confirm subsystems were running.

  3. User experience: The structured format with emoji section headers (🔑 🌐 🤖 🧩 📝) provided an at-a-glance dashboard feel. The current output looks like raw debug logs rather than a "gateway ready" confirmation.

  4. Troubleshooting: When the gateway restarts unexpectedly (health check triggered), the old format provided a clear "bookend" in logs that made it easy to identify restart boundaries. The new 3-line format is harder to spot in log files.

Suggestion:

Restore the previous structured startup log format from server-startup-log.ts, or make it configurable via a gateway.startupLogFormat: "structured" | "minimal" option. The structured format should include:

  • Auth mode and config source
  • Server URL/port
  • Agent model (provider/model)
  • Loaded plugins count and list
  • Log file path
  • Health monitor status
  • Heartbeat status

Environment:

  • OpenClaw version: 2026.4.25
  • OS: Windows 10.0.19045 (x64)
  • Affected file: dist/server-startup-log-*.js (compiled from src/gateway/server-startup-log.ts)

extent analysis

TL;DR

Restore the previous structured startup log format or make it configurable to improve visibility and troubleshooting.

Guidance

  • Review the server-startup-log.ts file to understand the changes made to the log output format.
  • Consider adding a configuration option gateway.startupLogFormat to allow users to choose between "structured" and "minimal" log formats.
  • Evaluate the importance of each log field (e.g., auth mode, server URL, agent model) and prioritize their inclusion in the log output.
  • Test the revised log format to ensure it meets the requirements for quick status visibility, health monitoring clarity, and user experience.

Example

// server-startup-log.ts
const startupLogFormat = 'structured'; // or 'minimal'
if (startupLogFormat === 'structured') {
  console.log('═══════════════════════════════════ 🐾 OpenClaw Gateway ═══════════════════════════════════');
  console.log(`🔑 Auth: ${authMode} (${configSource})`);
  console.log(`🌐 Server: ${serverUrl}`);
  console.log(`🤖 Agent: ${agentModel}`);
  console.log(`🧩 Plugins: ${plugins.length} loaded (${plugins.join(', ')})`);
  console.log(`📝 Log file: ${logFilePath}`);
} else {
  console.log(`agent model: ${agentModel}`);
  console.log(`ready (${plugins.length} plugins: ${plugins.join(', ')}; ${startupTime}ms)`);
  console.log(`log file: ${logFilePath}`);
}

Notes

The suggested solution assumes that the server-startup-log.ts file is the primary location for log output formatting. However, other parts of the codebase may also contribute to the log output.

Recommendation

Apply a workaround by modifying the `server

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#batch processing#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Feature Request: Restore formatted gateway startup log output [1 participants]