Cross-session message: sender label shows generic string instead of source session title

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 18, 2026

Description

When using the cross-session messaging feature (sending a message from one Claude Code session to another, e.g. via the session-messaging tool), the message content and push notification are delivered correctly, but the sender attribution header on the received message is wrong.

Expected: the received turn should be labelled "Message from {source session's title}" (in a Spanish-locale UI: "Mensaje de {título de la sesión origen}").

Actual: the header instead shows the generic feature/tool name, e.g. "Mensaje de Mensajes entre sesiones" ("Message from Cross-session Messages") — it does not resolve to the actual title of the sending session.

Steps to reproduce

  1. Have two active Claude Code sessions open, e.g. Session A (title "Diseñar clasificador semántico anti-hueco de detección") and Session B (title "Mensajes test").
  2. From Session A, send a message to Session B using the cross-session send-message capability.
  3. In Session B, observe the incoming user turn.

Expected behavior

Header reads: Mensaje de Diseñar clasificador semántico anti-hueco de detección (or the English equivalent Message from <Session A's title>).

Actual behavior

Header reads: Mensaje de Mensajes entre sesiones — a generic label unrelated to the sending session's actual title.

Additional notes

  • Message content and the push notification itself both arrive correctly — only the sender attribution label is wrong.
  • This was reported by the user as a recurring issue, observed across multiple separate tests over time, not a one-off.
  • Environment: Windows 11, Claude Code (desktop/CLI session-messaging feature).

I have a screenshot showing the mislabeled header if useful — happy to attach on request.

View original on GitHub ↗