Skip to content

fix(agent): persist WebUI transcript event timestamps - #524

Merged
Memtensor-AI merged 1 commit into
v1.1.8from
fix/memmy-434-webui-timestamps
Sep 22, 2026
Merged

Memtensor-AI merged 1 commit into
v1.1.8from
fix/memmy-434-webui-timestamps

Conversation

@syzsunshine219

Copy link
Copy Markdown
Collaborator

Problem

MEMMY-434 reports that WebUI JSONL rows have no event-level timestamp, so replay falls back to role order and can display a later assistant response with an earlier turn's time.

Change

Persist monotonic event timestamps at both GUI mirror and WebSocket transcript boundaries. Replay now prefers event timestamps while preserving legacy session-message fallback behavior.

Validation

  • npm --prefix App/memmy-agent exec vitest run tests/entrypoints/frontend-bridge/webui-transcript.test.ts tests/entrypoints/frontend-bridge/gui-transcript-sync.test.ts tests/integrations/channels/websocket-channel.test.ts

@syzsunshine219
syzsunshine219 force-pushed the fix/memmy-434-webui-timestamps branch from 773cdba to 90c24b9 Compare September 22, 2026 10:19
@syzsunshine219
syzsunshine219 marked this pull request as draft September 22, 2026 10:39
@Memtensor-AI
Memtensor-AI marked this pull request as ready for review September 22, 2026 11:01
@Memtensor-AI
Memtensor-AI merged commit 6742aae into v1.1.8 Sep 22, 2026
4 checks passed
@syzsunshine219
syzsunshine219 deleted the fix/memmy-434-webui-timestamps branch September 23, 2026 07:08
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