[Remote] Automatic session title changes are not synchronized to web history
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- distributed-systems, full-stack
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Open the same BitFun account in the desktop client and BitFun Remote.
- Start or open an assistant session whose title is automatically generated/renamed.
- Confirm the new title in the desktop client.
- 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.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 236
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 619
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GCWing/OpenBitFun
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GCWing/OpenBitFun#3213 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
GCWing/OpenBitFun#2363 ·
-
question
Difficulty 1/5 Under an hour Newbie friendliness 78/100
GCWing/OpenBitFun#2340 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
GCWing/OpenBitFun#3210 ·
-
GCWing/OpenBitFun#3195 · 2 comments · 1 assignee ·
All issues in GCWing/OpenBitFun
Similar issues
-
bug CLI custom-model
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rust-bitcoin/rust-bitcoin#6930 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fulcrumgenomics/ferro-hgvs#2251 ·
-
A-allocators A-docs C-enhancement T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100