#19516·lobehub

[Request] Agent-side tool to search previous conversations (topics + messages)

Author: thesobercoderCreated Sep 13, 2026Updated Sep 15, 2026

Requirement description

As an assistant running inside LobeHub, I have no tool to find a user's previous conversations on my own.

Today the assistant-side topic capability is limited to getTopicContext, which only works when the user explicitly references a specific topic (paste link / topic tag). There is no agent-callable way to:

  • list recent topics across sessions/agents
  • keyword / semantic search across topic titles and message contents
  • jump to a matching topic/message without the user hand-supplying the ID

UI search (topic keyword box, CMD+K global search) helps the human, but does not help the agent. Agent Memory extracts key facts, not a verbatim log, so it cannot answer "where did we discuss X?" or "find that message about Y".

Use cases

  • User: "find our earlier chat about Pulse pricing" -> agent should search and link it
  • User: "continue where we left off on the Railway runbook" -> agent should locate the topic
  • Cross-agent recall: user discussed something with another assistant and asks this one to pick it up

Proposed solution

Add an agent-callable search tool, e.g.:

  • searchTopics(query, scope?, limit) -> topic id, title, agent, updatedAt, snippet
  • searchMessages(query, topicId?, limit) -> message excerpt + topic reference
  • Respect existing visibility / permission / sync rules (local-first, cloud sync optional)

Keyword search is the minimum viable fix; semantic ranking would be a bonus. Reuse existing message indexing if available.

Related

  • #4930 [Request] Global Search Feature (closed as CMD+K supported)
  • #7043 More powerful topic content search (closed)
  • #1097 search for specific message records (closed)
  • #7422 Enhance global text search (closed as CMD+K)
  • #9654 Global Conversation Memory (closed, memory extracts facts, not verbatim search)
  • #16564 Dakera semantic cross-session recall (open, third-party backend proposal)

This request is distinct: it asks for the agent-side API, not another human UI affordance.

Environment

  • LobeHub self-hosted + Cloud
  • Assistant needs this without user-supplied topic IDs