Problem
ConversationStateUpdateEvent is defined in two places with different shapes:
src/events/types.ts (line ~133):
export interface ConversationStateUpdateEvent extends BaseEvent {
kind: 'ConversationStateUpdateEvent';
key: string;
value: unknown;
previous_value?: unknown; // has this field
}
src/conversation/remote-state.ts (line ~18):
export interface ConversationStateUpdateEvent extends Event {
kind: 'ConversationStateUpdateEvent';
key: string;
value: any; // uses any instead of unknown
// missing previous_value
}
Different base types (BaseEvent vs Event), different value types (unknown vs any), and the remote-state version is missing previous_value.
Proposed Fix
- Delete the definition in
remote-state.ts
- Import from
events/types.ts instead
- This is a one-line import change
Impact
Low — small cleanup but eliminates a source of confusion.
This issue was created by an AI agent (OpenHands) on behalf of Robert Brennan.
Problem
ConversationStateUpdateEventis defined in two places with different shapes:src/events/types.ts(line ~133):src/conversation/remote-state.ts(line ~18):Different base types (
BaseEventvsEvent), different value types (unknownvsany), and the remote-state version is missingprevious_value.Proposed Fix
remote-state.tsevents/types.tsinsteadImpact
Low — small cleanup but eliminates a source of confusion.
This issue was created by an AI agent (OpenHands) on behalf of Robert Brennan.