bax-10684-chat-member-display-bug

Disable group-derived chat members when their groups are deleted.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/octkp/dotfiles --skill bax-10684-chat-member-display-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bax-10684-chat-member-display-bug
Source: https://github.com/octkp/dotfiles/tree/main/claude/skills/bax-10684-chat-member-display-bug
Command: npx skills add https://github.com/octkp/dotfiles --skill bax-10684-chat-member-display-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Investigates and fixes an inconsistency where the member list shows more members than the member edit screen, and where members removed from groups can still access rooms.

Core Features & Use Cases

  • Root cause analysis: identifies API filtering differences between the member list and the member edit screen, specifically /api/v1/chat/room/users vs /api/v1/chat/room/members.
  • Fix implementation: updates backend logic so group-derived members are disabled when the user group is deleted, ensuring consistency across interfaces.
  • Reference and repair workflow: points to related backend/frontend files and data repair guides to align data integrity across systems.

Quick Start

Run the repair workflow to disable orphaned group-derived chat members in affected rooms.

Frequently Asked Questions about bax-10684-chat-member-display-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my chat member list show more users than the member edit screen?

Inconsistent chat member visibility occurs when API filtering differences exist between the member list and edit screen endpoints. Group-derived members remain visible if backend logic fails to disable them after user group deletion.

How do I fix orphaned chat members still accessing rooms after group deletion?

To fix orphaned chat members, run a backend repair workflow that identifies deleted group relationships, filters them by related_to, and updates chatmember_is_disabled to true across affected rooms.

What causes inconsistent chat member visibility between /api/v1/chat/room/users and /api/v1/chat/room/members?

Inconsistent chat member visibility happens when these two API endpoints apply different filtering logic for group-derived members. The backend must uniformly disable access when the source user group is deleted.

How do I disable group-derived chat members when a user group is deleted?

Disable group-derived chat members by updating backend logic to mark chatmember_is_disabled as true when group deletion occurs. This ensures member lists and editing screens remain consistent.

Can I repair orphaned chat member relationships without writing custom SQL?

You can repair orphaned chat member relationships by executing the built-in repair workflow. It automatically identifies orphaned relationships filtered by related_to and updates the disabled flag accordingly.

What are the limitations of fixing chat member display bugs by only updating the frontend?

Updating only the frontend fails to resolve data integrity issues because orphaned group-derived members remain active in the backend. The backend must disable these members to prevent unauthorized room access.