feat(pageUI): set default visibility of floating button to hidden, only show during tool invocation

[zzcr]

feat(pageUI): 将浮动按钮的默认可见性设置为隐藏，仅在工具调用期间显示

Pull Request (OpenTiny NEXT-SDKs)

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build-related changes
• CI-related changes
• Documentation-related changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coderabbitai]

Walkthrough

A floating widget's default visibility state is changed from true to false in the pageUI component. The widget now initializes as hidden and displays only when status transitions to "run" via existing runtime logic.

Changes

Cohort / File(s)	Summary
Widget Visibility State packages/next-wxt/components/pageUI.vue	Changed default floating widget visibility from true to false, hiding it on initial render and showing it only when status becomes "run".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A widget that once showed its eager face,
Now hides away in secret place.
When status runs, it springs to view—
A timely trick the defaults knew! ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: hiding the floating button by default and showing it only during tool invocation, which matches the code modification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into dev
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch zzc/feat-pageui-0214

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/next-wxt/components/pageUI.vue (1)

40-52: ⚠️ Potential issue | 🟠 Major

Floating button never auto-hides when tool invocation ends.

The PR states the button should "only show during tool invocation," but visible is set to true on status === 'run' (line 43) and is never set back to false when the status returns to 'ready'. The only way to hide the button is via the manual close button. If the intent is to auto-hide after the tool call completes, add an else branch:

Proposed fix

 const updateAnimationStatus = (data: { status: string; message: string }) => {
   if (data.status === 'run') {
     sendRuntimeMessage('focus-current-tab', data, 'content->bg')
     visible.value = true // Ensure visible when running
+  } else {
+    visible.value = false
   }

If the current behavior (stay visible until manually closed) is intentional, consider updating the PR description/comment on line 19 to reflect that.