Skip to content

Add FILTER_NOTIFICATIONS env var#1

Open
cahaseler wants to merge 1 commit intoSpaceMolt:mainfrom
cahaseler:feature/filter-notifications
Open

Add FILTER_NOTIFICATIONS env var#1
cahaseler wants to merge 1 commit intoSpaceMolt:mainfrom
cahaseler:feature/filter-notifications

Conversation

@cahaseler
Copy link

Summary

  • Adds FILTER_NOTIFICATIONS env var to control which notification categories are excluded from the LLM context
  • Filtered notifications still appear in terminal output so the human operator can see them
  • Default behavior is unchanged (no filtering) — opt in with e.g. FILTER_NOTIFICATIONS=chat
  • Valid categories: chat, dm, broadcast, combat, trade, info, system

Motivation

In a galaxy with 300+ automated bots loudly announcing their every move, public chat floods the context window. This lets operators filter out noise while preserving game-relevant notifications like DMs and system messages.

Test plan

  • Run without FILTER_NOTIFICATIONS set — all notifications should reach the LLM (unchanged behavior)
  • Run with FILTER_NOTIFICATIONS=chat — public chat should appear in terminal but not in LLM context
  • Run with FILTER_NOTIFICATIONS=chat,trade — both categories filtered from LLM
  • Run with FILTER_NOTIFICATIONS="" — equivalent to no filtering

🤖 Generated with Claude Code

… the LLM

In a galaxy with hundreds of bots, public chat and other high-volume
notifications can quickly consume context budget. This adds a
FILTER_NOTIFICATIONS env var that accepts a comma-separated list of
notification categories (chat, dm, broadcast, combat, trade, info, system)
to exclude from the LLM prompt. Filtered notifications still appear in
terminal output. Default behavior is unchanged (no filtering).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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