Hey EdgeType, I found two bugs in Better DeepSeek. First, when I go back and re-open an old chat while BDS is enabled, it creates a duplicate new chat with the same question I asked before. This doesn't happen when BDS is off, so it seems like the extension is re-submitting the last prompt when it re-renders the sidebar.
Second, the export/import format is mismatched. When I export my Stored Memory, Skills, RP Characters, or Saved Items, it downloads as a .json file — but when I try to import, it only accepts .md files. So I can't actually restore any of my backups. It would be great if export and import used the same format, or if import accepted both .json and .md.
ISSUE 1 — DUPLICATE CHAT CREATED WHEN RE-OPENING AN OLD CONVERSATION
SEVERITY: Medium — breaks chat continuity and fragments history
SUMMARY
When the Better DeepSeek (BDS) extension is enabled, navigating back to
an existing conversation and re-opening it causes a new, duplicate chat
to appear in the sidebar. The duplicate contains the same user question
that was previously asked in the original chat. This behavior does not
occur when BDS is disabled.
STEPS TO REPRODUCE
- Enable the Better DeepSeek extension.
- Start a chat and ask a question (for example, "How do tags work?").
- Leave the chat and open a different conversation or navigate away.
- Return to the sidebar and click the original chat to re-read it.
- Observe the chat list.
EXPECTED BEHAVIOR
The original chat opens normally and resumes in the same thread. No new
chat should be created.
ACTUAL BEHAVIOR
A new chat entry appears in the sidebar containing the same question that
was previously asked. The original chat remains, producing a duplicate
that clutters the list and breaks conversation continuity.
IMPACT
- Chat history becomes fragmented and duplicated.
- Re-reading old conversations becomes unreliable.
- Workflow is disrupted for users who review past discussions frequently.
- Duplicates may consume extra message quota or pollute search and tag
results.
ADDITIONAL OBSERVATIONS
- The problem occurs only when BDS is enabled. With BDS disabled,
re-opening the same chat does not create a duplicate.
- The issue appears related to BDS modifying the sidebar and re-rendering
the chat list, which may cause the active chat ID to be lost and the
last cached prompt to be re-submitted as a new session.
- Tags, pins, and search filtering appear unaffected, but they do not
prevent the duplicate from being created.
POSSIBLE CAUSE (HYPOTHESIS)
BDS re-initializes its UI layer when an old chat is re-opened. During
this re-render, the extension either re-submits the last cached message
or fails to restore the original conversation ID, causing the platform
to treat the re-open as a brand-new session.
SUGGESTED FIX DIRECTION
- Preserve the active chat ID across BDS re-renders.
- Avoid re-injecting the last prompt when resuming an existing
conversation.
- Decouple BDS's sidebar metadata (pins, tags) from the chat session
restore logic.
Hey EdgeType, I found two bugs in Better DeepSeek. First, when I go back and re-open an old chat while BDS is enabled, it creates a duplicate new chat with the same question I asked before. This doesn't happen when BDS is off, so it seems like the extension is re-submitting the last prompt when it re-renders the sidebar.
Second, the export/import format is mismatched. When I export my Stored Memory, Skills, RP Characters, or Saved Items, it downloads as a .json file — but when I try to import, it only accepts .md files. So I can't actually restore any of my backups. It would be great if export and import used the same format, or if import accepted both .json and .md.
ISSUE 1 — DUPLICATE CHAT CREATED WHEN RE-OPENING AN OLD CONVERSATION
SEVERITY: Medium — breaks chat continuity and fragments history
SUMMARY
When the Better DeepSeek (BDS) extension is enabled, navigating back to
an existing conversation and re-opening it causes a new, duplicate chat
to appear in the sidebar. The duplicate contains the same user question
that was previously asked in the original chat. This behavior does not
occur when BDS is disabled.
STEPS TO REPRODUCE
EXPECTED BEHAVIOR
The original chat opens normally and resumes in the same thread. No new
chat should be created.
ACTUAL BEHAVIOR
A new chat entry appears in the sidebar containing the same question that
was previously asked. The original chat remains, producing a duplicate
that clutters the list and breaks conversation continuity.
IMPACT
results.
ADDITIONAL OBSERVATIONS
re-opening the same chat does not create a duplicate.
the chat list, which may cause the active chat ID to be lost and the
last cached prompt to be re-submitted as a new session.
prevent the duplicate from being created.
POSSIBLE CAUSE (HYPOTHESIS)
BDS re-initializes its UI layer when an old chat is re-opened. During
this re-render, the extension either re-submits the last cached message
or fails to restore the original conversation ID, causing the platform
to treat the re-open as a brand-new session.
SUGGESTED FIX DIRECTION
conversation.
restore logic.