Cairn

Cross-platform session continuity and context sharing

NousResearch/hermes-agent · cluster 4335 · agent

Data as of

7 open items. Fix attempted, not merged.

The short answer

6open issues
1open PR
19items grouped
Known?
Yes. 19 related items grouped here, 12 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
6 issues and 1 PR.

These issues and pull requests all request the ability to share, transfer, or synchronize conversation sessions and context across different interfaces and platforms (CLI, Telegram, iMessage, desktop app, etc.). A recurring theme is enabling seamless handoff or mirroring of ongoing conversations between surfaces without losing history or context.

Open issues6

  • Issue#4335Feature Request: Cross-platform session context sharing (CLI ↔ Telegram)
  • Issue#17193[Feature]: Cross-session management across gateways and mediums
  • Issue#37612Group desktop sessions by source, not just host OS
  • Issue#44846Cross-channel session awareness
  • Issue#62780Canonical cross-platform session
  • Issue#67794[Feature]: Some Gatewway sessions don't appear under a unique session tab in Hermes Desktop

Open PRs1

  • PR#125893feat(desktop): give every gateway platform its own sidebar session group
Closed issues · 12
  • Closed#8366Feature: Cross-Platform Session Handoff (CLI ↔ Telegram ↔ iMessage)
  • Closed#18457Feature Proposal: First-Class Cross-Surface Session Continuity for Gateway Platforms
  • Closed#20458[Feature Request] Cross-platform session sharing via identity links
  • Closed#25544Feature Request: Cross-platform session sharing (e.g. WeChat + Feishu seamless context handoff)
  • Closed#28426[Feature] Cross-platform shared context
  • Closed#43928[Feature]: Feature Request: Cross-interface session and history synchronization
  • Closed#45275[Feature]: “Unified session history across Desktop app and Telegram”
  • Closed#49730Cross-platform conversation continuity (shared session context across Telegram, iMessage, CLI, etc.)
  • Closed#52030Feature Request: Show gateway platform sessions (Telegram, Discord, etc.) in desktop sidebar
  • Closed#52314Feature Request: Cross-Platform Session Continuity — share conversation context between CLI and Gateway
  • Closed#54981[Feature]: Cross-platform session continuity — resume a Desktop/CLI session from Telegram (and vice versa)
  • Closed#68301Native session bridging: mirror one conversation across surfaces (desktop <-> Telegram)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.07: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
12
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/4335.json
cluster/4335.md