[FIX] Issue with should show splash for PearAI chat

[charlwillia6]

Description ✏️

When PearAI first loaded I saw this:

When we should be seeing this:

This PR fixes that issue. I only saw the splash on new chats, but not when PearAI first loads

Also fixed: Open button handling in inventoryPage.tsx. This was supposed to be a separate PR, but I accidentally pushed the commit to this branch. The supermaven open button stopped working, and I updated the open handling for the search and mem0 sidebar.

Checklist ✅

• I have added screenshots (if UI changes are present).
• I have done a self-review of my code.
• I have manually tested my code (if applicable).

---

Important

Fixes splash screen display issue for PearAI chat by adjusting shouldShowSplash logic in gui.tsx.

• Behavior:
  • Fixes splash screen display issue in gui.tsx by setting shouldShowSplash to isNewSession.
  • Removes useWebviewListener for highlightedCode to prevent premature splash screen hiding.
• Misc:
  • Adds AUTO_COMPLETE_PROJECT.md with architecture details for auto-complete features.

^{This description was created by for d8385b7. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to d8385b7 in 1 minute and 39 seconds

More details

• Looked at 193 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 drafted comments based on config settings.

1. gui/src/pages/gui.tsx:181

• Draft comment:
  Assigning shouldShowSplash directly to isNewSession removes the ability to toggle splash visibility after initial load. Is this change intentional?
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  The splash screen appears to be a welcome screen that should only show when there's no chat history. The old code allowed it to be toggled with setShouldShowSplash, but this seems unnecessary - the splash is meant to be a welcome screen only. The new code correctly ties it directly to isNewSession. The removed highlightedCode event handler that was toggling it off seems unrelated to the splash's purpose.
  Maybe there was a legitimate need to hide the splash screen in certain scenarios even during a new session that I'm not seeing? The removed event handler suggests there was some intentional behavior being removed.
  Looking at the full context, the splash is clearly meant to be a welcome screen showing keyboard shortcuts. There's no logical reason it should be toggleable - it should simply show when there's no history and hide when there is history. The old event handler appears to have been an unnecessary complexity.
  This comment should be deleted. The change simplifies the splash screen behavior to match its intended purpose as a welcome screen.

2. gui/src/pages/gui.tsx:346

• Draft comment:
  The webview listener for "highlightedCode" that previously hid the splash has been removed. Confirm this is intended.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50%
  The removal of the highlightedCode listener appears to be intentional since it was replaced with a simpler, more direct approach - shouldShowSplash is now just tied to isNewSession. The old approach of using a listener to hide the splash seems more complex than necessary. The comment is asking for confirmation of an intentional change, which violates our rules about not asking for confirmations.
  The change could potentially break some functionality if the highlightedCode event was used for other purposes beyond just hiding the splash screen.
  The code shows a clear refactoring to simplify the splash screen logic. If there were other dependencies on this event, they would likely be visible in the codebase or cause build failures.
  This comment should be deleted because it's asking for confirmation of an intentional change, which violates our rules. The code changes show a clear refactoring that simplifies the logic.

3. AUTO_COMPLETE_PROJECT.md:12

• Draft comment:
  Typo: "TabAutocomleteOptions" should be "TabAutocompleteOptions".
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  While this is technically a typo, the review rules emphasize focusing on substantive issues that require code changes. This is a documentation file, and the typo is minor and doesn't affect functionality. The rules emphasize not making purely informative comments or obvious corrections.
  The typo could potentially cause confusion when developers look for this type in the codebase. It might make searching for references more difficult.
  While searchability is a concern, this is still a very minor documentation issue. The context makes it clear what is meant, and the actual type definition in code would be the source of truth.
  This comment should be deleted as it's a minor documentation typo that doesn't affect functionality and falls under the category of "obvious" or "unimportant" comments that the rules say to avoid.

4. gui/src/pages/gui.tsx:181

• Draft comment:
  Consider removing the redundant variable 'shouldShowSplash'. Since it's set to 'isNewSession', you can directly use 'isNewSession' in rendering.
• Reason this comment was not posted:
  Marked as duplicate.

5. gui/src/pages/gui.tsx:346

• Draft comment:
  Removal of the 'highlightedCode' listener is intentional to rely solely on 'isNewSession'. Verify that this change aligns with desired UX since the splash now can’t be manually hidden.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_HKMpS8jIKPTnU60o

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[nang-dev]

Yo charl, there are cases when this isnt right. like when you cmd+L code

[charlwillia6]

@nang-dev So are you saying you don't want the splash to show when you CTRL+L?

[nang-dev]

Yes

[charlwillia6]

Interesting. Okay. I'll work on that.