Skip to content

Comments

fix(macos): auto-scroll to bottom when sending message while scrolled up#2471

Merged
gumadeiras merged 3 commits intoopenclaw:mainfrom
kennyklee:kennyklee/auto-scroll-on-send
Jan 27, 2026
Merged

fix(macos): auto-scroll to bottom when sending message while scrolled up#2471
gumadeiras merged 3 commits intoopenclaw:mainfrom
kennyklee:kennyklee/auto-scroll-on-send

Conversation

@kennyklee
Copy link
Contributor

Summary

  • Auto-scroll to bottom when user sends a message, even if scrolled up reading history
  • Uses onChange(of: isSending) to detect when user starts sending
  • Sets isPinnedToBottom = true so subsequent messages also auto-scroll

Test plan

  • Build ClawdbotKit package
  • Scroll up in chat to read old messages
  • Send a new message - should scroll to bottom
  • Response appears at bottom where user can see it

Fixes #2470

🤖 Generated with Claude Code

@gumadeiras gumadeiras self-requested a review January 27, 2026 04:30
kennyklee and others added 3 commits January 26, 2026 23:41
When the user sends a message while reading older messages, scroll to
bottom so they can see their sent message and the response.

Fixes openclaw#2470

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@gumadeiras gumadeiras force-pushed the kennyklee/auto-scroll-on-send branch from c6ee3c2 to ba89c19 Compare January 27, 2026 04:45
@gumadeiras gumadeiras merged commit d2b5037 into openclaw:main Jan 27, 2026
15 of 23 checks passed
gumadeiras added a commit that referenced this pull request Jan 27, 2026
@gumadeiras
Copy link
Member

gumadeiras commented Jan 27, 2026

Landed via temp rebase onto main.

  • Gate: pnpm lint && pnpm build && pnpm test (FAILED, unrelated to changes: pairing-messages.test.ts, clawdbot-gateway-tool.test.ts)
  • Land commit: 4c2d8ee
  • Merge commit: 9135304

Thanks @kennyklee!

tyler6204 added a commit that referenced this pull request Jan 27, 2026
* fix(voice-call): validate provider credentials from env vars

The `validateProviderConfig()` function now checks both config values
AND environment variables when validating provider credentials. This
aligns the validation behavior with `resolveProvider()` which already
falls back to env vars.

Previously, users who set credentials via environment variables would
get validation errors even though the credentials would be found at
runtime. The error messages correctly suggested env vars as an
alternative, but the validation didn't actually check them.

Affects all three supported providers: Twilio, Telnyx, and Plivo.

Fixes #1709

Co-Authored-By: Claude <[email protected]>

* Add per-sender group tool policies

* fix(msteams): correct typing indicator sendActivity call

* fix: require gateway auth by default

* docs: harden VPS install defaults

* security: add mDNS discovery config to reduce information disclosure (#1882)

* security: add mDNS discovery config to reduce information disclosure

mDNS broadcasts can expose sensitive operational details like filesystem
paths (cliPath) and SSH availability (sshPort) to anyone on the local
network. This information aids reconnaissance and should be minimized
for gateways exposed beyond trusted networks.

Changes:
- Add discovery.mdns.enabled config option to disable mDNS entirely
- Add discovery.mdns.minimal option to omit cliPath/sshPort from TXT records
- Update security docs with operational security guidance

Minimal mode still broadcasts enough for device discovery (role, gatewayPort,
transport) while omitting details that help map the host environment.
Apps that need CLI path can fetch it via the authenticated WebSocket.

* fix: default mDNS discovery mode to minimal (#1882) (thanks @orlyjamie)

---------

Co-authored-by: theonejvo <[email protected]>
Co-authored-by: Peter Steinberger <[email protected]>

* fix(security): prevent prompt injection via external hooks (gmail, we… (