continuedev / continuedev/continue
IntelliJ plugin hijacks End key
Open
Nobody has claimed this yet.
ide:jetbrains
kind:bug
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Before submitting your bug report
- I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
- I'm not able to find a related conversation on GitHub discussions that reports the same bug
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: Windows 11
- Continue version: 1.0.67
- IDE version: 2026.1.1
- Model: Build #IU-261.23567.138
Description
https://youtrack.jetbrains.com/issue/IJPL-244168/TOML-End-key-navigates-to-wrong-location
To reproduce
- Open any .toml file
- Type a heading [some_heading]
- Press the End key.
Expected:
Caret should move to end of the line
Actual result:
Continue hijacks key input despite no autocomplete suggestion (blank suggestion)
Log output
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.
Research direction
Reproduce the issue on Windows 11 with Continue 1.0.67, the listed IDE version, and a TOML file, then trace the IntelliJ plugin's key handling around autocomplete when no suggestion is shown. Done means pressing End moves the caret to the end of the line without Continue hijacking the input or showing a blank suggestion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100