Skip to content

Discord: add ignored channel/category filters#93

Closed
thewilloftheshadow wants to merge 1 commit intoopenclaw:mainfrom
thewilloftheshadow:shadow/ignored-categories
Closed

Discord: add ignored channel/category filters#93
thewilloftheshadow wants to merge 1 commit intoopenclaw:mainfrom
thewilloftheshadow:shadow/ignored-categories

Conversation

@thewilloftheshadow
Copy link
Copy Markdown
Member

@thewilloftheshadow thewilloftheshadow commented Jan 2, 2026

More optional config options for Discord since it has so many channel/guild/user options for messages to come in! This lets you filter specific channels, as well as entire categories, from being responded to at all by Clawdis. It comes in two optional arrays inside the Discord config that get checked before passing the messages off.

@steipete
Copy link
Copy Markdown
Contributor

steipete commented Jan 2, 2026

Thanks for the PR! We just landed a new Discord config model and removed legacy keys. The current version of this PR adds legacy top‑level fields (discord.ignoredChannels / discord.ignoredCategories), which now conflicts with the new schema.

New model (current main):

  • discord.dm controls DMs (allowlist, group DM toggle).
  • discord.guilds is keyed by guild id (preferred) with optional slug.
  • Per‑guild requireMention plus per‑channel overrides in discord.guilds..channels.
  • Session display names now show discord:#.

How to express the same intent today:

  • Use a channel allowlist (deny‑by‑default) via discord.guilds..channels for the channels you want Clawdis to respond in.
  • If you still want a deny list for categories/channels, we can add it under the new schema, e.g.:
    • discord.guilds..ignoredChannels
    • discord.guilds..ignoredCategories
      (ids or slugs, per‑guild scope)

Because the legacy keys were removed, I’m going to close this PR as‑is. If you want to re‑target this feature, I’m happy to help rework it into the new structure.

@steipete
Copy link
Copy Markdown
Contributor

steipete commented Jan 2, 2026

Closing as legacy config keys were removed; recommend re-targeting to discord.guilds.* allow/ignore lists if still needed.

@steipete steipete closed this Jan 2, 2026
@steipete
Copy link
Copy Markdown
Contributor

steipete commented Jan 2, 2026

I added this in a different way - we overlapped a bit with my bed work. thanks!!

dgarson referenced this pull request in dgarson/clawdbot Feb 7, 2026
feat: meridia wiring integrations
dalefrieswthat pushed a commit to dalefrieswthat/openclaw that referenced this pull request Feb 25, 2026
* feat: scaffold evaluation harness foundation

* docs: add evaluation harness extension workstream note

* UX: add ChannelBroadcastCenter — unified messaging broadcast and channel management (openclaw#324)

* feat(evals): catalog schema + tool-reliability & agent-spawning scenarios (11 new cases)

- catalog.ts: ScenarioCatalog schema with category/difficulty grouping,
  CataloguedEvaluationCase type, filterCatalog, validateScenarioMetadata
- fixtures.ts: createDefaultCatalog, loadScenarios*, getCatalogStats CI loaders
- cases/hitl-escalation.ts: escalation-smoke + timeout-handling (ported from jerry/eval-scenario-schema)
- cases/memory-recall.ts: recall-context + path-traversal (ported from jerry/eval-scenario-schema)
- cases/tool-reliability.ts: 6 new deterministic scenarios
  - dispatch-success: happy-path tool invocation
  - dispatch-unknown-tool: graceful structured error on unknown name
  - retry-on-transient-failure: retry succeeds on nth attempt
  - max-retries-exhausted: retry gives up cleanly at limit
  - timeout-abort: AbortSignal propagation cuts execution early
  - result-schema-validation: validates ok/error result shape contracts
- cases/agent-spawning.ts: 5 new deterministic scenarios
  - basic-spawn-and-complete: child agent lifecycle + result accessible to parent
  - depth-limit-enforcement: spawn rejected beyond MAX_SPAWN_DEPTH=3
  - result-routing-to-requester: result delivered to correct session only
  - orphan-cleanup-on-parent-kill: recursive kill propagates to all descendants
  - parallel-completion-ordering: N concurrent agents collect without loss
- catalog.test.ts: 37 tests covering catalog build, filter, validation,
  per-category smoke runs (all 42 suite tests green)
- index.ts: updated exports for all new symbols

All scenarios: deterministic, no LLM calls, no external services.
Catalog now: 16 cases across 5 categories.

* UX: add ProviderRoutingPanel — AI provider routing and failover dashboard (openclaw#325)

* feat(evals): add JSONL export adapter for CI integration

- export-jsonl.ts: writeEvaluationJsonl writes each case as separate JSON line
- writeEvaluationJsonlSummary writes aggregate metrics in single line
- computeMetrics calculates per-suite, per-category, per-difficulty pass rates
- Supports append mode for incremental CI reporting
- 7 new tests covering path resolution, append, summary, and metrics

* feat(evaluation-harness): add WORKSTREAM.md and basic benchmark test

* feat(evals): add scenario catalog schema + 2 benchmark scenarios (HITL + memory) (openclaw#96)

- Add scenario catalog schema/metadata contracts in catalog.ts
- Add HITL benchmark scenarios (escalation + timeout handling)
- Add Memory path benchmark scenarios (context recall + path traversal)
- Add CI-friendly fixture loading in fixtures.ts
- Add comprehensive validation tests for catalog functionality
- Export all new types and cases from index.ts

Implements eh-002 with seed for eh-003 (5-scenario target)

* feat(evals): add tool-reliability benchmark scenario (4 cases) (openclaw#97)

* feat(evals): add scenario catalog schema + 2 benchmark scenarios (HITL + memory)

- Add scenario catalog schema/metadata contracts in catalog.ts
- Add HITL benchmark scenarios (escalation + timeout handling)
- Add Memory path benchmark scenarios (context recall + path traversal)
- Add CI-friendly fixture loading in fixtures.ts
- Add comprehensive validation tests for catalog functionality
- Export all new types and cases from index.ts

Implements eh-002 with seed for eh-003 (5-scenario target)

* feat(evals): add tool-reliability benchmark scenario (4 cases)

Adds the tool-reliability benchmark scenario to reach the 5-scenario target:
- tool-reliability.dispatch-smoke: basic tool dispatch structure validation
- tool-reliability.timeout-handling: tool timeout detection and handling
- tool-reliability.failure-recovery: fallback behavior on tool failure
- tool-reliability.result-validation: tool result structure validation

Wired through existing catalog + fixture loading utilities.
Updated tests to cover new scenarios.

eh-003 complete: 5-scenario target now met (was 4, added 4)

* Delete WORKSTREAM.md
github-actions bot pushed a commit to Piboonsak/openclaw_github that referenced this pull request Mar 9, 2026
zhyongrui added a commit to zhyongrui/openclaw that referenced this pull request Mar 20, 2026
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.

2 participants