GCWing / GCWing/OpenBitFun

[Remote] Automatic session title changes are not synchronized to web history

Abierto
#2,362 0 comentarios 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
Rust
Estrellas
2.3k
Forks
231
Merge medio
2 h 49 min
PR fusionados (30 d)
589

Descripción

## Bug
A session title that is automatically renamed in the desktop client is not reflected promptly in BitFun Remote.

## Expected behavior
When the desktop client changes a session title, the same title should appear in the remote session history immediately or after a short, bounded delay.

## Actual behavior
The title changes locally, but the remote history continues to show the old title until the session list is fetched again. This is especially confusing when several sessions are active.

## Reproduction
1. Open the same BitFun account in the desktop client and BitFun Remote.
2. Start or open an assistant session whose title is automatically generated/renamed.
3. Confirm the new title in the desktop client.
4. Open or return to the remote session history and observe the old title.

## Environment
- BitFun 0.2.17
- macOS desktop client
- BitFun Remote web UI via relay

## Notes
The desktop-side session metadata is updated. The remote client appears to update its local store only for a rename performed from the web UI and does not handle an incoming session-title update event from the desktop side.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Trace the desktop client's session metadata update, the incoming session-title update event, the BitFun Remote local store, and the remote session history refresh path. Reproduce with the listed desktop and web clients, then verify that an automatic desktop rename reaches remote history immediately or within the agreed bounded delay without requiring a session-list fetch.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
rust
Área
distributed-systems, full-stack
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
55/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.