Skip to content

SDK/Gateway: normalize or suppress raw chat events in run.events() #8

@BunsDev

Description

@BunsDev

Live dogfood finding

During the live OpenMeow SDK dogfood run, run.events() returned a usable normalized stream, but it also emitted raw events whose underlying Gateway event was chat and whose payload looked like assistant delta content.

Evidence doc:

Observed event sequence included:

run.started
assistant.delta
raw
assistant.delta
assistant.delta
assistant.delta
assistant.delta
assistant.delta
assistant.delta
run.completed

The raw event payload had raw.event: "chat" and assistant text fragments under message.content.

Impact

OpenMeow can render from assistant.delta, but app UIs need to either ignore/debug-log these raw events or risk duplicate assistant deltas.

Desired contract

For SDK-facing run.events():

  • either normalize chat assistant delta payloads into stable assistant.delta / assistant.message events, or
  • suppress duplicate raw chat deltas from the high-level run event stream and reserve them for rawEvents() / debug APIs.

Acceptance

  • Live OpenMeow happy-path run has no raw/debug fallback for normal assistant text streaming.
  • Raw provider/Gateway payloads remain available for debugging without being required for app UI rendering.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions