clawwork-ai/ClawWork

[Bug] System error messages missing sessionKey in ensemble mode

Open

#214 opened on Mar 31, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (63 forks)github user discovery
area/coregood first issuehelp wantedkind/bug

Repository metrics

Stars
 (519 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

packages/core/src/services/gateway-dispatcher.ts — when error messages are added via store.addMessage(taskId, 'system', errMsg), no sessionKey is included. In ensemble mode with multiple concurrent sessions, this makes it impossible to correlate errors to specific conductor/performer sessions.

Meanwhile, user and assistant messages already include sessionKey.

Expected behavior

Pass sessionKey to addMessage() for system messages generated during session event handling, or add it as metadata after creation.

Files

  • packages/core/src/services/gateway-dispatcher.ts — error handling in handleChatEvent() and handleAgentLifecycleStream()
  • packages/core/src/stores/message-store.ts — addMessage() signature may need an optional sessionKey param

Context

Introduced in PR #210.

Contributor guide

Research direction
Examine the addMessage calls in gateway dispatcher.ts and identify where sessionKey should be included. Modify the addMessage signature in message store.ts to accept an optional sessionKey parameter, then update the call sites in gateway dispatcher.ts to pass the sessionKey when available.
Tech stack
typescript
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75