support chat draft

[qdaxb]

Related GitHub Issue

Closes: #5306

Description

Save the content to localStorage regularly to avoid permanent loss of the text being entered

Test Procedure

• Enter text
• Restart the plugin
• The previous text should still be displayed in the input box

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Additional Notes

Get in Touch

---

Important

Adds chat draft persistence using localStorage with a new useChatTextDraft hook in ChatTextArea.tsx.

• Behavior:
  • Implements chat draft persistence using localStorage in ChatTextArea.tsx.
  • Introduces useChatTextDraft hook to auto-save drafts every 5 seconds, restore on mount, and clear on send.
  • Replaces onSend with handleSendAndClearDraft to clear drafts after sending.
• Functions:
  • useChatTextDraft: Manages draft lifecycle with localStorage.
  • handleSendAndClearDraft: Clears draft and calls onSend.
• Misc:
  • Adds import for useChatTextDraft in ChatTextArea.tsx.

^{This description was created by for c307066c1a00412f8209162e6f674186e6b4cf7a. You can customize this summary. It will automatically update as commits are pushed.}

[daniel-lxs]

Hey @qdaxb, Thank you for your contribution!

I left some suggestions that are worth taking a look at, let me know if you have any questions!

[daniel-lxs]

I did some research on using localStorage with VS Code extensions, and it seems the general consensus is that it's better to use the ExtensionContext and choose between globalState or workspaceState, depending on the use case.

Roo Code doesn't use localStorage except in very specific cases, so I think it makes sense to follow that pattern for this draft implementation as well.

Curious to hear what you think!

[qdaxb]

I did some research on using localStorage with VS Code extensions, and it seems the general consensus is that it's better to use the ExtensionContext and choose between globalState or workspaceState, depending on the use case.

Roo Code doesn't use localStorage except in very specific cases, so I think it makes sense to follow that pattern for this draft implementation as well.

Curious to hear what you think!

I think this makes the implementation a bit more complex, but considering future maintenance costs, it’s acceptable.
I’ve already made the changes according to the ExtensionContext approach.

[daniel-lxs]

Hey @qdaxb, I left a couple of suggestions that are worth taking a look at. Let me know if you have any questions!

[daniel-lxs]

Is there a potential race condition here? The draft is only restored if !inputValue, but what happens if the component receives an initial value before the message handler is set up? Could we miss restoring a valid draft in that case?

[daniel-lxs]

The pre-check using inputValue.length > MAX_DRAFT_BYTES * 2 might be too conservative. For strings with many multi-byte characters (like emojis or non-Latin scripts), this could reject valid drafts prematurely. Would it make sense to adjust this heuristic or document why 2x was chosen?