Enhancements and fixes to autocomplete behaviour

[bdavj]

Description

Autocomplete behaviour enhancements and fixes to remedy issues with repeat requests and timeouts (#4413).

• Re-surfacing control within the user configuration GUI for debounce delay
• Adding control within user configuration for autocomplete model timeout
• Fixing issues around debounce delay whereby

Screenshots

Testing Instructions

Configuration Verification

• Open user configuration GUI
• Verify presence of new debounce delay and timeout controls
• Confirm settings are persisted after modification

Functionality Testing

• Set various debounce delays and observe completion timing
• Test with longer model timeouts for complex completions
• Verify multi-line completions display correctly

Validation Steps

• Monitor .continue/prompt.log for completion responses
• Confirm completions only trigger after configured debounce delay
• Verify all lines of multi-line completions appear in IDE

Edge Cases

• Test with minimal and maximum timeout values
• Verify behavior with rapid consecutive typing
• Check completion behavior across different file types

Related Issues

• Fixes #4413 - Autocomplete timing and multi-line display issues

[netlify[bot]]

✅ Deploy Preview for continuedev canceled.

Name	Link
🔨 Latest commit	762dc34efe103a8f31713cf14982dc8dc16e61b2
🔍 Latest deploy log	https://app.netlify.com/sites/continuedev/deploys/680b5390fc8fbc0008e07c51

[bdavj]

Thanks @tomasz-stefaniak - seeing (what looks like?) an environmental test failure. Is this something external to the PR? Is there an updated dependency / configuration i need to merge back in? Thanks

[bdavj]

Hi @tomasz-stefaniak - I'm keen to get this merged, however main is moving quickly and we end up with merge conflicts quicker than I can get this reviewed. Would it be possible to assist here? Many thanks

[vincentkelleher]

@bdavj your contribution looks great :+1:

If I understand well, the debounce settings would also be available through the config.yaml file ? :innocent:

[bdavj]

@vincentkelleher - This is only through the GUI currently.

[bdavj]

@vincentkelleher @tomasz-stefaniak - Would it be possible to rereview this please now that its in line with main again? Thanks

[sestinj]

Hi @bdavj, yesterday we shared some updates with our contributors about how we're aiming to improve the contribution process. Part of this included the addition of a Contributor License Agreement (CLA) to protect both contributors and the project. We're reaching out to ask that previous contributors sign it.

Could you please take a moment to sign, or if you have any questions send me a message? (either here or [email protected] would work)

To do so, you just need to post a comment below with the following text:

I have read the CLA Document and I hereby sign the CLA

❤️ Thank you for the work you've done on Continue, and let me know if you have any suggestions on how we can make the project even better!

[github-actions[bot]]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

0 out of 2 committers have signed the CLA.
:x: @Ben Jones
:x: @bdavj
Ben Jones seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}