fix: clarify 24h window reminder behavior#223
Open
awsl233777 wants to merge 1 commit intomainfrom
Open
Conversation
📝 WalkthroughWalkthroughThis PR updates the 24-hour WeChat window feature documentation and user-facing text to clarify that the system provides expiry reminders rather than automatic renewal. Users are reminded shortly before the window expires and can manually reply with any message to refresh the window. Message text in reminders and UI labels have been updated accordingly across documentation, backend messaging, and frontend components. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Around line 142-145: The English README still claims "auto session renewal"
which contradicts the Chinese clarification about reminder-only behavior; find
the English section that mentions "auto session renewal" (e.g., the "Multiple
Bot Management" / "Multi-Bot management" paragraph) and update the wording to
match the Chinese note — replace claims of automatic background renewal with a
clear statement that Hub only provides "pre-expiry reminders" and that users
must reply to the message to restart the 24-hour window; ensure the English text
mirrors the Chinese explanation and removes any implication of silent/automatic
renewal.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 164166cb-d77a-4f09-8092-9fab17e805de
📒 Files selected for processing (5)
README.mdinternal/bot/manager.goweb/src/pages/bot-detail.test.tsxweb/src/pages/bot-detail.tsxweb/src/pages/bots.tsx
Comment on lines
+142
to
145
| **多 Bot 管理** · 扫码绑定多个微信号，统一面板看状态，到期前提醒防掉线。 | ||
|
|
||
| > 说明：微信 24 小时窗口目前不能由 Hub 在后台静默自动续期。Hub 现在支持的是“到期前提醒”，会在窗口快到期时提醒你回一条消息，收到回复后窗口会重新开始计时。 | ||
|
|
There was a problem hiding this comment.
English section still contradicts the new reminder-only behavior.
The Chinese clarification is good, but README.md Line 472 still says “auto session renewal,” which conflicts with this PR’s corrected behavior and can mislead English users.
📝 Proposed doc fix
-- **Multi-bot management** — Bind and manage multiple WeChat accounts, auto session renewal
+- **Multi-bot management** — Bind and manage multiple WeChat accounts, expiry reminders before the 24-hour window ends🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README.md` around lines 142 - 145, The English README still claims "auto
session renewal" which contradicts the Chinese clarification about reminder-only
behavior; find the English section that mentions "auto session renewal" (e.g.,
the "Multiple Bot Management" / "Multi-Bot management" paragraph) and update the
wording to match the Chinese note — replace claims of automatic background
renewal with a clear statement that Hub only provides "pre-expiry reminders" and
that users must reply to the message to restart the 24-hour window; ensure the
English text mirrors the Chinese explanation and removes any implication of
silent/automatic renewal.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Issue #221 was caused by product copy overstating the current capability. The code only supports reminder-before-expiry, while the docs/UI claimed automatic renewal. That mismatch led users to expect hands-free renewal and treat the later 409 conflict as a bug in the renew flow.
Validation
ok github.com/openilink/openilink-hub/internal/bot (cached)
Closes #221
Summary by CodeRabbit
Documentation
Bug Fixes