home_logo slot always visible and cannot be dismissed in TUI

[kn0wsnothing]

home_logo slot always showing on new update. takes up half the tui and is not dismissable

---

Metadata

Field	Value
CLI Version	0.9.4
Platform	darwin
Architecture	arm64
OS Release	25.5.0
Category	bug

[kn0wsnothing]

Follow-up with more detail from binary inspection (v0.9.4, darwin/arm64). Confirming the mechanism and why there's no user-facing escape hatch right now.

What renders, and why it's always visible

The home view (packages/tui/.../home.tsx) renders the home_logo slot with mode: "replace", defaulting to WelcomePanel:

createComponent2(pluginRuntime.Slot, {
  name: "home_logo",
  mode: "replace",
  get children() { return createComponent2(WelcomePanel, {}); }   // default
})

WelcomePanel itself has only one state-conditional element — the "Connect your AI model to start." line, gated by !useReady():

createComponent2(Show, {
  get when() { return !ready(); },   // ready = isAnyProviderConnected() || setupComplete()
  get children() { /* "Connect your AI model to start." */ }
})

The logo + "What is Altimate Code" blurb is unconditional — it renders every launch regardless of provider/connection state. setupComplete is an in-memory Solid signal initialized to false each launch (createSignal(false)); it is not persisted to config, DB, or a file. So there is no "already seen" state to flip.

No internal plugin registers home_logo, so the slot has zero entries and falls back to WelcomePanel via the resolvedEntries.length === 0 branch of the Slot reconciler.

Why a user plugin can't hide it either

A user TUI plugin can register home_logo, but returning null/undefined/false does not suppress the default — the mode: "replace" reconciler treats that as "no plugin output" and falls back to renderFallback(), which is the default children (WelcomePanel):

if (mode2 === "replace") {
  const renderedEntries = resolvedEntries.map((entry) => renderEntry(entry));
  const hasPluginOutput = renderedEntries.some((entry) => entry !== null && entry !== undefined && entry !== false);
  if (!hasPluginOutput) {
    return renderFallback();   // <- back to WelcomePanel
  }
  return renderedEntries;
}

So the only plugin-side workaround is to return a non-null empty box (e.g. a zero-height <box>), which relies on the undocumented home_logo slot name and the replace/fallback semantics — fragile across versions.

Request

A config flag to suppress the panel would be the durable fix. Something like:

// altimate-code.json
{
  "tui": { "home_logo": false }   // or: "onboarding": { "show_welcome_panel": false }
}

…which would either skip rendering the home_logo slot's default child, or register an internal no-op home_logo slot so the panel doesn't appear. Thanks!

[githnm]

@kn0wsnothing - Thanks for flagging this. I'm taking a look and will get back to you shortly.