Skip to content

Routing: skip WhatsApp allowlist for non-WhatsApp#96

Closed
thewilloftheshadow wants to merge 1 commit intoopenclaw:mainfrom
thewilloftheshadow:shadow/discord-dm-fix
Closed

Routing: skip WhatsApp allowlist for non-WhatsApp#96
thewilloftheshadow wants to merge 1 commit intoopenclaw:mainfrom
thewilloftheshadow:shadow/discord-dm-fix

Conversation

@thewilloftheshadow
Copy link
Copy Markdown
Member

@thewilloftheshadow thewilloftheshadow commented Jan 2, 2026

This fixes #89, since DMs were implemented but being falsely filtered. The Discord setup handles its own whitelist, but it was being re-whitelisted again in the Whatsapp checks where it was checking for discord:123456789012345678 and was failing.

Previous logs:

Skipping auto-reply: sender discord:439223656200273932 not in allowFrom list

@steipete
Copy link
Copy Markdown
Contributor

steipete commented Jan 2, 2026

Fixed this by creating a new whatsapp config block. Thanks!

@steipete steipete closed this Jan 2, 2026
slathrop referenced this pull request in slathrop/openclaw-js Feb 11, 2026
Phase 16: Gateway + Cron + iOS
- 20 upstream commits mapped with full diff analysis
- Cron dependency chain identified (#46 -> #96 -> #142)
- 50+ downstream files verified, all confirmed present
- 5-wave execution structure recommended
- New directories identified (extensions, scripts/dev)

Co-Authored-By: Claude Opus 4.6 <[email protected]>
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
CyberSpencer added a commit to CyberSpencer/openclaw that referenced this pull request Mar 19, 2026
…_actions/actions/setup-python-6

chore(deps): bump actions/setup-python from 5 to 6
0x666c6f added a commit to 0x666c6f/openclaw that referenced this pull request Mar 26, 2026
…po mapping (openclaw#96)

* fix(sre:PLA-902): move label enforcement post-normalization, fix curator repo mapping

Label enforcement was in the message_sending hook which runs BEFORE
markdownToSlackMrkdwnChunks(). The converter treats *Label:* as
Markdown italic and outputs _Label:_, undoing the fix.

Fix: move enforceIncidentLabelFormat() to src/slack/format.ts and
apply post-normalization in both Slack send paths. The plugin hook
now only handles progress-message blocking.

Also: add prime-monorepo mapping for Curator App V2 to SKILL.md
Gotchas section — bot was searching consumer-monorepo and archived
morpho-vault-admin instead of the correct repo.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

* fix(sre:PLA-902): add prime-monorepo mapping to all knowledge surfaces

Added prime-monorepo app mapping (all 7 apps + shared packages) to:
- SKILL.md: dedicated "Prime Monorepo App Mapping" section with
  app/path/domain/sentry table
- knowledge-index.md: source-of-truth table + fast routing entry
- runbook-map.md: symptom->runbook row + repo routing entry
- repo-root-model.md: common cases with app and package paths

Bot was searching consumer-monorepo and archived morpho-vault-admin
for curator/prime bugs — all three knowledge surfaces now route to
the correct repo.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

* fix(sre:PLA-902): simplify regex, expand label detection coverage

- Drop redundant lookbehind in label regex — `^` with `m` flag
  already matches after newlines
- Expand INCIDENT_LABEL_BOLD_RE to cover all 15 labels (was only 5)

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
lucian-why pushed a commit to lucian-why/openclaw that referenced this pull request Mar 28, 2026
Bumps the docker-images group with 1 update: debian.


Updates `debian` from `98f4b71` to `74d56e3`

---
updated-dependencies:
- dependency-name: debian
  dependency-version: bookworm-slim
  dependency-type: direct:production
  dependency-group: docker-images
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: sjhu <[email protected]>
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.

Feature: support both @ mentions and DM's in discord

2 participants