Skip to content

[CHA-1699] Add Future Channel Bans support #217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
totalimmersion wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

[CHA-1699] Add Future Channel Bans support #217

totalimmersion wants to merge 1 commit into from

Conversation

@totalimmersion
Copy link
Contributor

@totalimmersion totalimmersion commented Jan 17, 2026

Summary

Add support for the Future Channel Bans feature.

New Parameters

  • ban_from_future_channels parameter in channel.ban_user() method
  • remove_future_channels_ban parameter in client.unban_user() method

Usage

# Ban user from current channel and all future channels created by banner
channel.ban_user("user-id", ban_from_future_channels=True, reason="spam")

# Remove future channel ban (does NOT remove existing channel bans)
client.unban_user("user-id", remove_future_channels_ban=True, channel_cid="messaging:channel-id", created_by="banner-user-id")

# Query future channel bans
response = client.query_future_channel_bans(filter_conditions={"created_by_id": "banner-user-id"})

Related PRs

Linear

  • CHA-1699

🤖 Generated with Claude Code

@totalimmersion @claude
feat: [CHA-1699] add Future Channel Bans support
e1100ae 
- ban_from_future_channels and remove_future_channels_ban are automatically
  supported via **options kwargs in ban_user and unban_user methods
- Add query_future_channel_bans method to query FCBs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@10printhello 10printhello Awaiting requested review from 10printhello 10printhello will be requested when the pull request is marked ready for review 10printhello is a code owner

@slavabobik slavabobik Awaiting requested review from slavabobik slavabobik will be requested when the pull request is marked ready for review slavabobik is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@totalimmersion