Skip to content

feat(search): message search for conversations and web console#22

Merged
one-ea merged 1 commit into
mainfrom
260629-feat-message-search
Jun 29, 2026
Merged

feat(search): message search for conversations and web console#22
one-ea merged 1 commit into
mainfrom
260629-feat-message-search

Conversation

@one-ea

@one-ea one-ea commented Jun 29, 2026

Copy link
Copy Markdown
Owner

Summary

  • ConversationService.searchMessagesInConversation — per-topic LIKE search with ESCAPE for % and _ wildcards
  • ConversationService.searchMessages — global cross-conversation search with pagination, JOIN to contacts and telegram_topics
  • /search <keyword> command in Topic — returns up to 20 matches with message previews
  • /operations/search web page — search box + paginated results table (conversation, topic, contact, direction, text preview)
  • Navigation header adds "搜索" tab

Problem

/history only showed the last 30 messages. There was no way to find a specific message by keyword across conversation history or globally. Ops had to SQL query the database to find past messages.

Verification

  • npm run verify passed (check + 48 tests + audit 0 vulns)
  • 3 new test cases: per-conversation search accuracy, global search with pagination, web search page HTML rendering

- Add ConversationService.searchMessagesInConversation for per-topic
  LIKE search with ESCAPE for % and _ wildcards
- Add ConversationService.searchMessages for global cross-conversation
  search with pagination, JOIN to contacts and telegram_topics
- Add /search <keyword> command in Topic, returns up to 20 matches
- Add /operations/search web page with search box and paginated
  results table showing conversation, topic, contact, direction, text
- Navigation header adds 搜索 tab
- 3 new test cases: per-conversation search, global search with
  pagination, web search page rendering
Co-authored-by: monkeycode-ai <monkeycode-ai@chaitin.com>
@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@one-ea, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f415ee6e-90ab-470a-86a6-b2cbc5a19efa

📥 Commits

Reviewing files that changed from the base of the PR and between 44b9689 and 406394d.

📒 Files selected for processing (5)
  • src/channels/telegram/commands.ts
  • src/domain/conversations.ts
  • src/runtime/main.ts
  • src/runtime/web-console.ts
  • test/core.test.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 260629-feat-message-search

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

Comment @coderabbitai help to get the list of available commands.

@one-ea one-ea merged commit c79c322 into main Jun 29, 2026
4 checks passed
@one-ea one-ea deleted the 260629-feat-message-search branch June 29, 2026 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants