Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Render statusline before MCP/plugin initialization completes

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…

The statusline (configured via settings.json → statusLine.command) doesn't render until the entire session initialization is complete — including all MCP server connections and plugin loading. On setups with many MCP servers/plugins, this means the statusline is invisible for 20-30 seconds after Claude Code starts.

Root Cause

The statusline (configured via settings.json → statusLine.command) doesn't render until the entire session initialization is complete — including all MCP server connections and plugin loading. On setups with many MCP servers/plugins, this means the statusline is invisible for 20-30 seconds after Claude Code starts.

RAW_BUFFERClick to expand / collapse

Summary

The statusline (configured via settings.json → statusLine.command) doesn't render until the entire session initialization is complete — including all MCP server connections and plugin loading. On setups with many MCP servers/plugins, this means the statusline is invisible for 20-30 seconds after Claude Code starts.

Problem

The statusline command itself executes in <1s, but it isn't invoked until after all MCP servers connect and plugins load. With ~24 MCP servers and 60+ plugins, session initialization takes 20-30s. During this time the user sees no statusline — no model info, no context usage, no cost tracking.

Proposed Change

Invoke the statusline command early in the startup sequence (e.g., right after parsing settings and before MCP/plugin initialization begins). The statusline input JSON could contain partial/default values for fields not yet available. This gives users immediate visual feedback while MCP servers connect in the background.

Environment

  • Windows 11, CLI
  • 24 MCP servers, 60+ enabled plugins
  • statusLine.type: "command"

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING