Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Architecture: User-Centric Sessions v2

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Migration from chat-centric to user-centric sessions with per-platform configuration, shared group memory, and user-specific tool usage.

Root Cause

Migration from chat-centric to user-centric sessions with per-platform configuration, shared group memory, and user-specific tool usage.

RAW_BUFFERClick to expand / collapse

Summary

Migration from chat-centric to user-centric sessions with per-platform configuration, shared group memory, and user-specific tool usage.

Key Features

  1. Per-Platform Session Mode: Telegram user-centric, Discord chat-centric, etc.
  2. Shared Group Memory: Common chat history visible to all users in groups
  3. User-Specific Tool State: Composio actions, GitHub credentials, etc. isolated per user
  4. Clean System Prompt: No metadata pollution - context injected as message prefix or tool context

Use Case

In group chats, users share the conversation history (planning, brainstorming) but each user has their own tool credentials and action history. For example:

  • User A uses Composio to create a GitHub issue (only they see the tool call)
  • User B uses Composio to create a branch (only they see their tool call)
  • Both see each other's text messages in the shared chat history

Architecture Plan

Full plan committed at: https://github.com/gthieleb/hermes-agent/blob/main/docs/architecture-plans/user-centric-sessions-v2.md

Implementation Phases

PhaseContentTime
1Per-Platform Config2h
2Session Key Builder v22h
3Shared Group Memory3-4h
4User-Specific Tool State3-4h
5Message Routing (no system prompt metadata)3h
6Tool Context Injection2-3h

Total: 19-23h

Backward Compatibility

  • Default remains chat_centric (opt-in per platform)
  • Legacy sessions auto-migrate on /reset
  • Env var overrides available

Related Code

  • gateway/session.py - Session key building
  • gateway/run.py - Message handling
  • gateway/platforms/telegram.py - Platform adapter
  • agent/prompt_builder.py - System prompt construction

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#conversation history#SSR setup#ISR setup#authentication setup#request error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING