hermes - 💡(How to fix) Fix [Feature] Cross-platform shared context [1 comments, 2 participants]

title: "[Feature] Cross-platform shared context / unified memory across sessions" labels: enhancement

Problem

Hermes runs across multiple platforms (CLI, Telegram, Discord, Feishu, etc.), but each platform's session is fully isolated. This creates three real pain points:

1. Context lost across platforms — User starts a conversation on Telegram, switches to CLI, and the CLI agent has no idea what was discussed on Telegram. The user has to repeat themselves.
2. Conflicting instructions — User tells one instance "use model X", tells another "use model Y", both instances remember different things.
3. Repeated work — User has to re-explain preferences, environment details, or ongoing tasks when switching platforms.

Proposed Solution

1. Cross-platform shared context file

A lightweight, file-based approach that works with existing infra:

• A shared file (e.g. ~/.hermes/shared_context.md) that all platform instances read at session start
• Agents write key decisions, active tasks, and environment changes to this file
• The system prompt or a startup hook can auto-inject the last N lines of this file as context

2. Cross-platform session linking (optional, more involved)

• A /topic enhancement that can link sessions across platforms by topic ID
• When a user messages on Telegram with context of an existing CLI session, the agent can session_search and bridge the gap automatically
• Optional: auto-tag sessions with the originating platform so the agent knows "this user was just on Telegram about X"

3. Proactive cross-session awareness (quick win)

• Before processing a user message, the agent automatically runs session_search() with a broad query to check recent activity across all platforms
• This is already possible with the existing session_search tool — the issue is that the agent doesn't know it should do this

Implementation Sketch

# At agent startup / message processing:
# 1. Read shared context
shared_ctx = read_file("~/.hermes/shared_context.md")

# 2. Search recent cross-platform sessions
recent = session_search(limit=5, sort="newest")

# 3. If significant activity found, inject into context
if recent has cross-platform activity:
    context_summary = summarize(recent)
    inject_system_hint(f"[Cross-platform context] {context_summary}")

Existing Capabilities That Already Support This

• session_search — can search across all sessions regardless of platform
• memory — shared across all profiles/platforms
• File read/write tools — can maintain a shared state file

The pieces are there — they just need to be wired together into a default behavior or a configurable feature.

Related

• Feature request: automatic cross-session context injection
• Would benefit all multi-platform users of Hermes