hermes - 💡(How to fix) Fix feat: Add /history slash command with prompt search & reuse for gateway platforms [2 pull requests]

feat: Add /history slash command with prompt search & reuse for gateway/Feishu platforms

Is your feature request related to a problem? Please describe. Currently, the /history slash command is only available in CLI mode. On gateway platforms (Feishu, Telegram, Discord, etc.), users cannot view their conversation history, search past prompts, or reuse previous prompts within the current session. This forces users to describe context manually or rely on the agent's memory, which is inefficient when they want to rerun a previous query, find a specific past prompt, or use a past prompt as a template.

Describe the solution you'd like Add a /history slash command for gateway platforms with two modes of operation and two interaction modes for reuse:

Usage:

• /history — Show recent history (last N messages, paginated 5 per page)
• /history <keyword> — Search history for prompts matching the keyword, return paginated results

Mode 1 — Interactive card selection (primary): On platforms supporting interactive cards/buttons (Feishu, Telegram, Discord), render results as a paginated interactive card with:

• 5 messages per page, each showing truncated text + a 复用 (Reuse) button
• Page navigation buttons at the bottom: "◀ Previous" / "Next ▶" + page indicator (Page 1/3)
• Tapping 复用 on a message immediately submits that prompt as a new user query
• The card updates in-place when navigating pages
• When searching (/history <keyword>), results are matched by semantic/keyword search against session history

Mode 2 — Reply by number (fallback): For platforms without interactive card support, show a numbered list:

📜 Session History — search "agent" (Page 1/3)
[1] "Write a FastAPI agent scheduling framework"
[2] "Deep research: Latest Agent Memory advances"  
[3] "Deploy hermes-agent to new server"
[4] "Analyze pros/cons of multi-agent collaboration"
[5] "Explain ReAct agent working principle"
---
◀ Previous | Next ▶

• Reply with a number to reuse that prompt
• Pagination via previous/next buttons

Describe alternatives you've considered

• Relying on the agent's session_search tool — works but requires describing what's being searched
• Exporting via hermes sessions export — too slow for real-time use
• Adding /resume in gateway — useful for whole-session resume but doesn't support selective prompt reuse

Additional context On Feishu specifically, the ideal UX is an interactive card with:

• 5 results per page, each with a 复用 button
• Page navigation buttons at the bottom
• Keyword search via /history <query> triggers session_search internally

Implementation notes:

• Search implementation can leverage existing session_search tool internally
• Feishu card: multi-page interactive card with value callback for button actions (复用 + page navigation)
• State management: track current page, search query, and result set per user/session
• Text fallback: numbered list for platforms without card support