Skip to content

fix(shim): tell refuses a nickname two sessions share (MUS-109) - #192

Merged
Castor-o7 merged 3 commits into
mainfrom
fix/tell-ambiguous-nickname
Nov 7, 2026
Merged

Castor-o7 merged 3 commits into
mainfrom
fix/tell-ambiguous-nickname

Conversation

@Castor-o7

Copy link
Copy Markdown
Owner

Reported by the watchman (mellow-weevil) after the same bug turned up in Marshal's port (marshal#168).

Problem. terminal_send::resolve_targets matched an id or a nickname with .find(). Nicknames repeat across restarts: today the ghost row 64a05eda and the live watchman 7195eda2 were both mellow-weevil. So muster-shim tell mellow-weevil could go to the ghost and still report the message as sent. That's the command rally digest uses to reach the watchman.

Change. An exact id still names one session. A nickname that matches several sessions is refused, and the error lists their ids: "mellow-weevil names 2 sessions (…); use one's id". An ambiguous id prefix was already handled this way.

Tests. a_nickname_two_sessions_share_is_refused_with_their_ids covers three cases:

  • the shared nickname is refused, and the error lists both ids
  • either session's id still reaches it
  • with only one session on the nickname, it resolves

Clippy passes.

🤖 Generated with Claude Code

Castor-o7 and others added 3 commits November 6, 2026 20:14
Nicknames repeat across restarts, so the first match could send a
terminal tell (and rally digest) to a ghost row and report it sent. A
nickname that names several sessions is now refused with their ids, as
an ambiguous prefix already was.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Castor-o7
Castor-o7 merged commit c9e0f1f into main Nov 7, 2026
10 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant